Information providing apparatus for performing data processing in accordance with order from user

ABSTRACT

This invention is a photosite which allows access from a cell phone to provide user-friendlier services. The photosite creates an ID (S 6501 ) and creates a character string Str from the ID by combining numerals and alphabetical characters by using a storage unit which stores buttons  0  to  9  of the cell phone and the number of alphabetical characters assigned to the respective buttons in correspondence with each other (S 6502 -S 6507 ). In this case, a character string is created such that any two consecutive characters are assigned to different keys.

FIELD OF THE INVENTION

The present invention relates to an information providing apparatuswhich provides data processing services for users.

BACKGROUND OF THE INVENTION

Recently, with improvements in communication infrastructures andadvances in information communication techniques, online informationproviding services which use the Internet and the like can be provided.Many of conventional systems for providing such services demand theinput of IDs from user terminals. If such an ID is constituted by onlynumerals, the ID can be easily input. In this case, however, as comparedwith a case wherein the same information is expressed by characters, thenumber of digits required becomes very large. This makes it inconvenientto notify or display the ID. In addition, the user has difficulty inmemorizing the ID.

Recently, therefore, many systems are designed to issue IDs constitutedby combinations of numerals and characters.

With improvements in communication infrastructures, users can accessinformation providing systems even from terminals having no keyboard,e.g., cell phones and fixed telephones, other than computers.

No conventional information providing systems, however, have issued IDsin consideration of facilitating input from terminals without anykeyboard.

When, for example, characters are to be input from a general telephone,three characters A, B, and C are assigned to the same button to whichthe numeral 2 is assigned. In general, when this button is pressed once,A is input; when pressed consecutively again, B is input; and whenfurther pressed again, C is input. When a given button A is pressedseveral times first, and then another button B is pressed, a characterassigned to the button A is input to the first character input column,and a character assigned to the button B is input to the next characterinput column. That is, when a different button is pressed, input by thepreceding button is confirmed.

When a three-character string AEI is to be input by using such atelephone, the user presses button 2 once, button 3 twice, and button 4three times. That is, the character string AEI can be input by pressingnumeral buttons a total of six times. However, when a character stringABC, which is an alphabetical character string having the same number ofcharacters as that of the above character string, is to be input, theuser must presses buttons a total of eight times, i.e., once for button2, once for the move button for character input columns, twice forbutton 2, once for the move button for the character input columns, andthree times for button 2. That is, the input operation becomescomplicated by the degree to which the move button for the characterinput columns must be pressed.

In addition, different operations are required to move character inputcolumns depending on the types of telephones, and the position of themove button is not fixed unlike the numeral buttons. It therefore takesmuch time for a user to become accustomed to input operation.

SUMMARY OF THE INVENTION

The present invention has been proposed to solve the above problem inthe prior art, and has as its object to provide user-friendlierservices.

According to the present invention, the foregoing object is attained byproviding an information providing apparatus which can be connected toan information processing apparatus, comprising: means for creatingnumerical data; storage means in which types of a plurality of keysarranged in the information processing apparatus and the number andtypes of characters assigned to the respective keys are stored incorrespondence with each other; and creating means for creating acharacter string from the numerical data by combining the characters,wherein the creating means creates a character string, on the basis ofthe types of keys and the number and types of characters assigned to therespective keys which are stored in the storage means, such thatconsecutive two characters are assigned to the different keys.

According to the present invention, the foregoing object is attained byproviding an information processing method using an informationproviding apparatus which can be connected to an information processingapparatus and includes storage means in which types of a plurality ofkeys arranged in the information processing apparatus and the number andtypes of characters assigned to the respective keys are stored incorrespondence with each other; comprising: a step of assigning uniquenumerical data to a user; and a creating step of creating a characterstring from the numerical data by combining the characters, wherein inthe creating step, a character string is created such that twoconsecutive characters are assigned to the different keys.

According to the present invention, the foregoing object is attained byproviding a control program for controlling an information processingapparatus which can be connected to an information processing apparatusand includes storage means in which types of a plurality of keysarranged in the information processing apparatus and the number andtypes of characters assigned to the respective keys are stored incorrespondence with each other, and processor; causing the processor toexecute: a step of assigning unique numerical data to a user; and acreating step of creating a character string from the numerical datasuch that two consecutive characters are assigned to the different keys.

Other features and advantages of the present invention will be apparentfrom the following description taken in conjunction with theaccompanying drawings, in which like reference characters designate thesame or similar parts throughout the figures thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram conceptually showing an information providingsystem according to an embodiment of the present invention;

FIG. 2 is a block diagram showing the schematic arrangement of theoverall information providing system according to the embodiment of thepresent invention;

FIG. 3 is a view showing a data table associated with customerinformation managed in a photosite according to the embodiment of thepresent invention;

FIG. 4 is a view showing a customer state table for managing informationrepresenting the current state of a user using the photosite accordingto the embodiment of the present invention;

FIG. 5 is a view showing a customer album data table managed in thephotosite according to the embodiment of the present invention;

FIG. 6 is a view showing an album information data table managed in thephotosite according to the embodiment of the present invention;

FIG. 7 is a view showing an album image data table managed in thephotosite according to the embodiment of the present invention;

FIG. 8 is a view showing an image information table managed in thephotosite according to the embodiment of the present invention;

FIG. 9 is a view showing an order information table managed in thephotosite according to the embodiment of the present invention;

FIG. 10 is a view showing an ordered image data table managed in thephotosite according to the embodiment of the present invention;

FIG. 11 is a view showing an order settlement data table managed in thephotosite according to the embodiment of the present invention;

FIG. 12 is a view showing an orderer data table managed in the photositeaccording to the embodiment of the present invention;

FIG. 13 is a view showing a printsite data table managed in thephotosite according to the embodiment of the present invention;

FIG. 14 is a view showing the contents of a database for managingphotosite information in a printsite according to the embodiment of thepresent invention;

FIG. 15 is a view showing the contents of an order information table ina printsite according to the embodiment of the present invention;

FIG. 16 is a view showing the contents of a print image informationtable in a printsite according to the embodiment of the presentinvention;

FIG. 17 is a view showing the contents of an order delivery table in aprintsite according to the embodiment of the present invention;

FIG. 18 is a view showing an example of the window to be displayed whena server service is started in the photosite according to the embodimentof the present invention;

FIG. 19 is a flow chart showing processing in the photosite when userregistration is performed with respect to the information providingsystem according to the embodiment of the present invention;

FIG. 20 is a view showing a window for user registration with respect tothe information providing system according to the embodiment of thepresent invention;

FIG. 21 is a view showing the error window to be displayed when dataconcerning a necessary item is not input at the time of userregistration in the photosite according to the embodiment of the presentinvention;

FIG. 22 is a view showing an example of the error window to be displayedwhen a login name has already been registered at the time of userregistration in the photosite according to the present invention;

FIG. 23 is a view showing a window for prompting a user to input apassword again at the time of user registration in the photositeaccording to the embodiment of the present invention;

FIG. 24 is a view showing an example of the warning window to bedisplayed when a password is wrong at the time of user registration inthe information providing system according to the embodiment of thepresent invention;

FIG. 25 is a view showing a user registration confirmation window in thephotosite according to the embodiment of the present invention;

FIG. 26 is a view showing an example of the contents of e-mail issued atthe time of user registration in the photosite according to theembodiment of the present invention;

FIG. 27 is a view showing an example of the window to be displayed whenthe user fails to log in on a service start window in the photositeaccording to the embodiment of the present invention;

FIG. 28 is a view showing the window to be displayed when the userproperly logs in to the photosite according to the embodiment of thepresent invention;

FIG. 29 is a flow chart showing processing associated with editoperation by the user in the photosite according to the embodiment ofthe present invention;

FIG. 30 is a flow chart showing a procedure for album edit processing inthe photosite according to the embodiment of the present invention;

FIG. 31 is a view showing an album property setting window in thephotosite according to the embodiment of the present invention;

FIG. 32 is a view showing an album e-mail notification setting window inthe photosite according to the embodiment of the present invention;

FIG. 33 is a view showing an album delete confirmation window in thephotosite according to the embodiment of the present invention;

FIG. 34 is a flow chart showing processing associated with albumselection and display when one of album selection buttons is pressed inthe photosite according to the embodiment of the present invention;

FIG. 35 is a view showing an example of an album detailed display windowin the photosite according to the embodiment of the present invention;

FIG. 36 is a flow chart showing a procedure for uploading images to acurrently displayed/edited album in the photosite according to theembodiment of the present invention;

FIG. 37 is a view showing a warning window indicating that no image canbe uploaded in the photosite according to the embodiment of the presentinvention;

FIG. 38 is a view showing an uploaded image selection window accordingto the embodiment of the present invention;

FIG. 39 is a view showing the warning window to be displayed when a fileother than images to be processed in the embodiment of the presentinvention is uploaded;

FIG. 40 is a flow chart showing processing for calculating the number offiles that can be added according to the embodiment of the presentinvention;

FIG. 41 is a flow chart showing the flow of processing among a clientPC, the photosite, and a printsite when a print order is to be placed byusing the photosite according to the embodiment of the presentinvention;

FIG. 42 is a view showing a printsite selection window according to theembodiment of the present invention;

FIG. 43 is a view showing an image print order window according to theembodiment of the present invention;

FIG. 44 is a view showing the estimate display window to be displayedwhen an image print order is placed according to the embodiment of thepresent invention;

FIG. 45 is a view showing the orderer information input display windowto be displayed when an image print order is placed according to theembodiment of the present invention;

FIG. 46 is a view showing the destination information input window to bedisplayed when an image print order is placed according to theembodiment of the present invention;

FIG. 47 is a flow chart showing the contents of temporary print orderissuing processing in the photosite according to the embodiment of thepresent invention;

FIG. 48 is a view showing the warning window to be displayed when noimage is selected at the time of print order processing according to theembodiment of the present invention;

FIG. 49 is a flow chart showing the contents of display processing for aprint image selection window in a printsite according to the embodimentof the present invention;

FIG. 50 is a flow chart showing estimation calculation in a printsiteand notification of estimate information to the photosite according tothe embodiment of the present invention;

FIG. 51 is a flow chart showing processing in the photosite in theinterval between the instant at which the estimate notified from theprintsite is acquired and the instant at which a formal print order isissued according to the embodiment of the present invention;

FIG. 52 is a view showing a benefit information setting window in thephotosite according to the embodiment of the present invention;

FIG. 53 is a view showing an example of the temporary print order formatnotified from the photosite to a printsite according to the embodimentof the present invention;

FIG. 54 is a view showing an example of the format of estimateinformation notified from the printsite to the photosite according tothe embodiment of the present invention;

FIG. 55 is a view showing an example of the formal print order formatnotified from the photosite to the printsite according to the embodimentof the present invention;

FIG. 56 is a view showing an example of the order contents confirmationwindow displayed in the information providing system according to theembodiment of the present invention;

FIG. 57 is a view showing an example of a service item data list in theprintsite according to the embodiment of the present invention;

FIG. 58 is a view showing an example of a benefit list in the printsiteaccording to the embodiment of the present invention;

FIG. 59 is a view showing an example of the e-mail to be notified when aprint order is placed according to the embodiment of the presentinvention;

FIG. 60 is a flow chart showing the details of formal print orderreception processing in the printsite according to the embodiment of thepresent invention;

FIG. 61 is a view showing an example of album notification mailaccording to the embodiment of the present invention;

FIG. 62 is a flow chart showing check digit embedding processing in thephotosite according to the embodiment of the present invention;

FIG. 63 is a view showing a list representing the relationship betweenthe buttons of a telephone and alphabetical characters input by pressingthe buttons according to the embodiment of the present invention;

FIG. 64 is a flow chart showing disclosure album ID creating processingin the photosite according to the embodiment of the present invention;

FIG. 65 is a flow chart showing the processing of associating numeralswith alphabetical characters and calculating buttons of a telephonewhich can input the alphabetical characters;

FIG. 66 is a view showing an album browse start window in theinformation providing system according to the embodiment of the presentinvention;

FIG. 67 is a view showing an album browse window in the informationproviding system according to the embodiment of the present invention;

FIG. 68 is a flow chart showing the processing of checking the ID inputwhen the user tries to browse an album in the information providingsystem according to the embodiment of the present invention;

FIG. 69 is a view showing the window to be displayed when no album isfound which corresponds to the ID input at the time of album browsing inthe information providing system according to the embodiment of thepresent invention;

FIG. 70 is a view showing the first window to be displayed when the userbrowses an album through a portable phone in the information providingsystem according to the embodiment of the present invention;

FIG. 71 is a view showing the window to be displayed when the userbrowses an album from the portable phone in the information providingsystem according to the embodiment of the present invention;

FIG. 72 is a view showing the first window to be displayed when the userbrowses an album from the portable phone;

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The preferred embodiments of the present invention will be described indetail below with reference to the accompanying drawings. Note that thepresent invention is not limited to the relative positions ofconstituent elements, display windows, and the like described in theembodiments unless otherwise specified.

First Embodiment

An information providing system according to an embodiment of thepresent invention which shares and provides digital image data throughthe Internet will be described.

In general, digital image information is provided by an image inputdevice. The following is a background to this trend. With smoothdecreases in semiconductor device size, the part sizes and costs of LSIsand solid-state image sensing elements which constitute image inputdevices represented by digital still cameras and digital video camerashave been scaled down. As a consequent, image input devices forphotographing images have been widely used.

For example, the image data photographed by a digital camera is storedin a memory inside the digital camera. The data is then transferred to arecording unit represented by an HDD or the like in a personal computerowned by the user of the digital camera and managed/stored or is writtenin an external recording medium such as a CD-R and stored. With thewidespread use of color scanners as well as digital cameras, images canbe easily created and stored as electronic data.

In consideration of such a situation, the information providing systemaccording to this embodiment includes an image service provider (to bereferred to as a photosite hereinafter) and print service provider (tobe referred to as a printsite hereinafter). This photosite providesservices like keeping the image data photographed by users using imageinput devices in storage areas in servers on the Internet and allowingcustomers to browse the image data again at the time they require it.The printsite prints out electronic documents such as New Year's cards,wordprocessed documents, and images which are transferred through theInternet, and provides the printed matter as merchandise.

The photosite according to this embodiment does not provide any printservice by itself but forms an affiliation with a printsite which canprovide various print services and gives a print order to the printsite.

<Outline of System>

An outline of the information providing system according to thisembodiment will be described with reference to FIG. 1. FIG. 1 is a viewshowing how data are exchanged among a PC (Personal Computer) 102 (to bereferred to as a user PC hereinafter) or portable terminal 113 such as amobile phone, PDA, and so on, that is used by a user who receivesservices, a photosite 105 which manages images and personal informationof the user, and a printsite 109 which manages print processing andprint unit prices between the instant at which the user generates arequest to browse images and the instant at which printed matter isacquired.

In step S1, the user accesses a Web server 121 in the photosite 105 byusing a browser 120 of the user PC 102, and generates a request tobrowse images stored in an image database (DB) 117 in the photosite 105.In step S2, the photosite 105 displays images on the browser 120 under apredetermined condition.

In step S3, the user selects an image to be printed out from the imagesbrowsed on the browser 120. In step S4, the identification informationof the selected image is transferred from the photosite 105 to theprintsite 109 (temporary print order). The flow advances to step S5, inwhich the printsite 109 adds information about a form (size and thelike) that can be printed out and causes a Web server 122 to present theuser PC 102 with the information together with the image, therebyprompting the user to input a print form, a print count, and the like.

In step S6, when the user inputs a print form, a print count, and thelike for each selected image through the browser 120 and sends a printinstruction 10 to the printsite 109, the printsite 109 calculates aprice (estimated price) requested to carry out the print instruction byusing a print information database 119 and price calculation module 110.

In step S7, when the printsite 109 temporarily transfers the estimatedprice to the photosite 105, the photosite 105 calculates a price(offered price) on the basis of the estimated price factoring in thepersonal information by using a personal information database 118 andprice calculation module 108.

In step S8, the photosite 105 causes the browser 120 of the user PC 102to display the presented price by using the Web server 121.

In step S9, if the user approves the presented price and the user PC 102returns an approval action to the photosite 105, a settlement module 107serving as a settlement means receives this action and performssettlement processing.

In step S10, the photosite 105 sends a formal print order to theprintsite 109. The printsite 109 sends the formal print order to theprintsite 109. Upon reception of the formal print order, the printsite109 performs printing in accordance with the formal print order by usingthe printing means owned by the printsite 109.

In step S11, the printsite 109 delivers printed matter 112 obtained byprinting to the destination designated by the user of the user PC 102,who has generated the print request, by a transportation means of somekind.

<Arrangement of System>

FIG. 2 is a view showing the detailed arrangement of the informationproviding system according to this embodiment.

Reference numeral 101 denotes an image input apparatus which converts anoptical image as image information into an electrical signal, performspredetermined image processing, and records/reproduces the resultantinformation as digital information. This image input apparatus may be adigital still camera capable of photographing a still image andrecording the image as image data or a digital video camera capable ofphotographing a moving image and recording the image as moving imagedata.

Reference numeral 102A denotes a user personal computer; and 116, a datatransfer interface for transferring image data photographed between theimage input apparatus 101 and the user PC 102A. The data transferinterface 116 may be a wire interface represented by USB (UniversalSerial Bus) or IEEE1394 or a wireless interface represented by IrDA orBluetooth.

The image data photographed by the image input apparatus 101 and storedas digital information is transferred to a storage area in aninformation storage unit represented by the HDD of the user PC 102Athrough the data transfer interface 116. For image data transfer fromthe image input apparatus 101 to the user PC 102A, the following twocases are present. In the first case, in accordance with an instructionfrom the OS or special software installed in the user PC 102A, the imagedata stored in the image input apparatus 101 are transferred at once. Inthe second case, in response to the instruction of a transfer commandfrom the image input apparatus 101, the OS or special software in theuser PC 102A ensures a data recording area in the information storageunit in the user PC 102A and transfers the image data to the area.

A browser 120A having a standard protocol capable of transmittinginformation on the Internet 104 can run on the user PC 102A. With thisbrowser 120A, a user can access the photosite 105 using the standardprotocol such as HTTP protocol to display Web information created by adescription language such as HTML or XML. Web information is linked tomultimedia information such as images or sounds managed by sites on theInternet 104. With this operation, the user of the user PC 102A canreceive services provided by the photosite 105 using the Internet 104.

The image data photographed by the image input apparatus 101 and storedin the information storage are in the user PC 102A is transferred to thephotosite 105 in accordance with a request from the user of the user PC102A (this transfer will be referred to as image upload hereinafter).This method of uploading an image includes a method in which image datato be transferred is selected using the above browser 120A andtransferred in synchronism with the action of requesting image uploadand a method in which image data is directly selected and transferred byusing image upload software. Either method is executed on the basis of aprotocol usable on the Internet, e.g., HTTP or FTP. A photo sharingmodule 106 is a module which executes this series of operations in thephotosite 105.

The photo sharing module 106 checks whether the uploaded image data isdata that can be used in the photosite 105. If it is determined that thedata can be used, the uploaded image data is stored in the imagedatabase 117, and its attribute information or the like is stored in thedatabase 118. The photosite 105 may put a plurality of uploaded imagedata into one unit and manage it as an album for browsing.

In this stage, the photo sharing module 106 notifies the user PC 102Athat the image data is normally uploaded. The user of the user PC 102Acan upload image data through the Web browser in this manner.

In addition to the above attribute information of image data, variousdata are collectively managed in the database 118. For example, suchdata include the data of user attribute information registered in thephotosite 105 and the data of attribute information of a printsite whichis requested to print out uploaded image data.

The flow of print order processing for uploaded image data will besequentially described next. The user of the user PC 102A can browse theimage data which is uploaded by himself/herself through the Web browser120A. The methods of selecting images to be browsed include a method ofselecting images to be sequentially browsed image by image, and a methodof registering a plurality of images as one album, selecting an album tobe browsed from a plurality of albums, and selecting/browsing each imagemanaged in the selected album.

The photosite 105 gives a print order for the image data uploaded fromthe user to a print provider which provides printouts of image data.This print provider is one of printsites 109A, 109B, and 109C. For thesake of illustrative convenience, only the three printsites areillustrated. However, the number of printsites is not specificallylimited and may be more than four.

The user of the user PC 102A selects image data which he/she wants toprint out so as to purchase the printed matter as merchandise from thebrowse window of the uploaded images. The user then selects a printsiteto which he/she wants to give an order from the printsites 109A, 109B,and 109C which the photosite 105 can provide. The user selects theprintsite 109 to which he/she gives an order in consideration of, forexample, the services provided by each printsite 109, unit price, anddelivery time. For the sake of descriptive convenience, the followingdescription will be made on the assumption that the user has selectedthe printsite 109A. Even if, however, the user selects the printsite109B or 109C, since the basic flow of information remains the same, adescription thereof will be omitted.

When the user selects image data for which he/she wants to give a printorder from the browse window, and notifies the photosite 105 of thecorresponding information, the photosite 105 creates, in a predeterminedform, a temporary print order associated with the image data for whichthe printout request has been given, and transmits it through theInternet 104, thereby requesting the printsite 109A to make an estimate.

Upon reception of the temporary print order from the photosite 105, theprintsite 109A acquires necessary image data from the image database 117in the photosite 105 and creates selected image information. Bytransmitting this selected image information to the user PC 102A throughthe Internet 104, the user can input a print form, a print count, andthe like for each selected image on the Web browser 120A of the user PC102A.

The printsite 109A calculates an estimated price by using a pricecalculation module 110A on the basis of the information such as theprint form and print count for each selected image, and transmits thecalculated estimated price to the photosite 105 through the Internet104.

The photosite 105 receives the information of the estimated pricetransmitted from the printsite 109A in real time. The photosite 105 thenchanges the received estimated price by using the price calculationmodule 108 in consideration of the personal information of the user.More specifically, the photosite 105 can accumulate “points” asalternative currency that functions as currency with respect to thephotosite 105 for each registered user. When the user is to use theaccumulated points, he/she can receive a discount on the print price inaccordance with the points.

The Web server 121 in the photosite 105 transfers the presented pricebased on the estimated price factoring in the points as Web informationto the user PC 102A, thereby dynamically presenting the price to theuser who gives a print order.

That is, when the user selects image data for which he/she wants to givea print order and the printsite 109 and inputs a print form, a printcount, and the like on the Web browser 120A of the user PC 102A, a pricerequired for the printing operation is quickly displayed.

When the user of the user PC 102A, who has given the print order,approves of purchasing the service at this presented price and returnsan approval action to the photosite 105, the settlement module 107serving as a settlement means receives this and performs settlementprocessing. When the settlement is completed, the photosite 105 sends aformal print order to the printsite 109A.

When the printsite 109A receives this formal print order, it isdetermined that the settlement is confirmed, and the flow advances toprint processing. In the print processing, first of all, the printsite109A acquires the image data required for printing out from the imagedatabase 117 in the photosite 105. The image data acquired in thismanner is printed out as printed matter 112A by a printer 111A connectedto the printsite 109A. The printed matter 112A is delivered, by sometransportation means, to the destination designated by the user of theuser PC 102A who has given the printout request. Referring to FIG. 2,the printer 111A is connected to the printsite 109A. However, thisprinter need not be connected to the printsite 109A as long as theprinter is under the control of the user of the printsite 109A.

The above description has been made on the outline of the systemdesigned to allow a user who has uploaded the image data photographed bythe image input apparatus 101 through the user PC 102A to browse theimage data in the photosite 105 and give a print order. In this case, asa terminal for uploading image data, a PC has been exemplified. However,the information providing system according to the present invention isnot limited to this. Image data may be uploaded from a portable terminalor may be directly uploaded from an image input apparatus such as adigital camera, digital video camera, scanner, or copying machine.

A method of allowing a person other than a user who has uploaded imagedata in the photosite 105 to browse the image data uploaded in thephotosite 105 and stored in the database 117 through the Internet 104will be described next.

The photosite 105 provides the third party designated by a user who hasuploaded images with browse and print order services with respect to the“uploaded images” or “album that manages a plurality of uploaded imagesas one archive”. The user who has uploaded the image data in thephotosite 105 notifies the photosite 105, by using the Web browser 120A,of the attribute information of a user (to be referred to as a browseuser hereinafter) who is permitted to browse the images, e.g., the nameof the browse user, and the e-mail address.

When disclosing images to the browse user, the photosite 105 creates aURL (Universal Resource Locator) required for disclosure. As the URL tobe created at this time, a unique address using a random number or thelike that cannot be uniquely predicted is assigned. The following is anexample:

http://◯◯

◯.com/PhotoSite/Album/AlbumEntry.cgi?AlbumID.=AJNWDMF (Such a URL thatcannot be uniquely predicted will be referred to as a random URLhereinafter.)

The photosite 105 notifies the browse user of the random URL created inthis manner by e-mail through the Internet 104 upon adding passwordinformation required for browsing to the e-mail as needed. Uponreception of the e-mail, the browse user accesses the Internet 104 froma user PC 102B, and inputs the random URL notified by the e-mail to aWeb browser 102B. This allows the browse user to browse the images andalbum designated by the user who has uploaded the images.

A method of allowing a browse user who uses the user PC 102B to give aprint order for image data that can be browsed in this manner will bedescribed next. The photosite 105 gives a print order for image datafrom the browse user to one of the printsites 109A, 109B, and 109C whichprovide printouts of image data.

The browse user of the user PC 102A selects image data which he/shewants to print out so as to purchase the printed matter as merchandisefrom the browse window. The browse user of the user PC 102B then selectsthe printsite 109 to which he/she wants to give an order from theprintsites 109A, 109B, and 109C which the photosite 105 can provide. Thebrowse user selects the printsite 109 to which he/she gives an order inconsideration of, for example, the services provided by each printsite109, unit price, and delivery time. For the sake of descriptiveconvenience, the following description will be made on the assumptionthat the user has selected the printsite 109B. Even if, however, theuser selects the printsite 109A or 109C, since the basic flow ofinformation remains the same, a description thereof will be omitted.

When the browse user selects image data for which he/she wants to give aprint order from the browse window, and notifies the photosite 105 ofthe corresponding information, the photosite 105 creates, in apredetermined form, a temporary print order associated with the imagedata for which the printout request has been given, and transmits itthrough the Internet 104, thereby requesting the printsite 109B to makean estimate.

Upon reception of the temporary print order from the photosite 105, theprintsite 109B acquires necessary image data from the image database 117in the photosite 105 and creates selected image information. Bytransmitting this selected image information to the user PC 102B throughthe Internet 104, the user can input a print form, a print count, andthe like for each selected image on the Web browser 120B of the user PC102B.

The printsite 109B calculates an estimated price by using a pricecalculation module 110B on the basis of the information such as theprint form and print count for each selected image, and transmits thecalculated estimated price to the photosite 105 through the Internet104.

The photosite 105 receives the information of the estimated pricetransmitted from the printsite 109B in real time. If the browse user hasno personal information, the estimated price transmitted from theprintsite 109B to the user PC 102B is transferred as Web information. Ifthe browse user has personal information, the presented price based onthe estimated price factoring in points is transferred as Webinformation, thereby dynamically presenting the price to the browse userwho has given the print order.

When the browse user of the user PC 102B, who has given the print order,approves of purchasing the service at this presented price and returnsan approval action to the photosite 105, the settlement module 107serving as a settlement means receives this and performs settlementprocessing. When the settlement is completed, the photosite 105 sends aformal print order to the printsite 109B. The printsite 109B receivesthis formal print order and acquires the image data required forprinting out from the image database 117 in the photosite 105. The imagedata acquired in this manner is printed out as a printed matter 112B bya printer 111B serving as a printing means owned by the printsite 109B.The printed matter 112B is delivered, by some transportation means, tothe browse user of the user PC 102B who has given the printout request.

The photosite 105 can provide the portable terminal owner designated bya user who has uploaded images with a service of making a notificationof browsing of images (or an album) and browse function and print orderservices. A user can also receives notification e-mail containing a URLfor browsing an album through a portable terminal, and at the same time,can browse images or an album or give a print order through the portableterminal (a user who uses the photosite 105 through a portable terminalwill be referred to as a portable browse user hereinafter).

The use who has uploaded image data from the user PC 102A to thephotosite 105 through the Internet 104 notifies the photosite 105, byusing the Web browser 120A, of the attribute information of a user whois permitted to browse the images, e.g., the name of the browse user,and the e-mail address.

In disclosing images and an album to a portable browse user, thephotosite 105 creates a random URL necessary for disclosure. Thephotosite 105 notifies a portable terminal 113A of the portable browseuser of the random URL by using e-mail upon adding password informationnecessary for browsing, as needed. This e-mail notified to the portablebrowse user is sent out from a mail distribution server in the photosite105 to a mobile network 114A, which can exchange various data with theportable terminal 113A, through the Internet 104 and an Internetconnection gateway 115A, and is transferred to the portable terminal113A. Upon reception of the e-mail, the portable browse user accessesthe photosite 105 through the route of the mobile network 114, Internetconnection gateway 115A, and Internet 104, by inputting the random URLaddress notified by the e-mail.

The photosite 105 has browser information dedicated to portableterminals, which is created by a description language dedicated toportable terminals, e.g., WML or CompactHTML, in addition to Webinformation created by a description language such as HTML or XML whichcan be displayed on the Internet 104. The photosite 105 also has imagedata resized to a size that can be displayed on the portable terminal113A. In accordance with a request from the portable terminal 113A, thephotosite 105 discriminates the model of the terminal, and transmitsinformation that can be displayed on the portable terminal 113A.According to an environment for portable terminals capable of browsing,pieces of browser information in various formats are prepared in thephotosite 105 to provide services for portable communication terminalsthat can browse the browser information, including not only the portableterminal 113A but also the portable terminal 113B that differs from theportable terminal 113A in communication protocol specifications,information description languages, and mobile network environments. Forthe sake of descriptive convenience, FIG. 2 shows only the two usableportable terminals, namely the portable terminals 113A and 113B.However, three or more portable terminals may be used.

A browse request from the portable terminal 113B is sent from a mobilenetwork 114B that can be used by the portable terminal 113B to anInternet connection gateway 115B. After protocol conversion, the requestis sent to the photosite 105 connected to the Internet 104. In additionto the Web display information created by a description language such asHTML or XML which can be browsed on the Internet 104, the photosite 105has the browser information created by a description language dedicatedto portable terminals, such as WML or CompactHTML by resizing image datato a size that can be browsed on the portable terminal 113B. Inaccordance with a request from the portable terminal 113B, the photosite105 discriminates the model of the terminal, and sends out informationthat can be browsed on the portable terminal 113B.

A method of allowing a portable browse user, i.e., the user of theportable terminal 113A or 113B, to select image data and give a printorder will be described next.

The transmission path of information between the photosite 105 and theportable terminal 113A is photosite 105→Internet 104→Internet connectiongateway 115A→mobile network 114A→portable terminal 113A.

The portable browse user can browse the images or album designed by theuser who has uploaded the images by inputting the random URL notified bye-mail to the browser of the portable terminal.

The portable browse user selects a printsite to which he/she wants togive an order from the printsites 109A, 109B, and 109C which thephotosite 105 can provide. The portable browse user selects theprintsite 109 to which he/she gives an order in consideration of, forexample, the services, unit price, and delivery time provided by eachprintsite 109. For the sake of descriptive convenience, the followingdescription will be made on the assumption that the user has selectedthe printsite 109C. Even if, however, the user selects the printsite109B or 109A, since the basic flow of information remains the same, adescription thereof will be omitted.

When the user selects image data for which he/she wants to give a printorder from the browse window, and notifies the photosite 105 of thecorresponding information, the photosite 105 creates a temporary printorder associated with the image data for which the printout request hasbeen given, and transmits it through the Internet 104, therebyrequesting the printsite 109C to make an estimate.

Upon reception of the temporary print order from the photosite 105, theprintsite 109C acquires image data necessary for selected windowinformation from the image database 117 in the photosite 105 and createsselected image information. By transmitting this selected imageinformation to the portable terminal 113A through the Internet 104, theportable browse user can input a print form, a print count, and the likefor each selected image on the portable terminal 113A.

The printsite 109C calculates an estimated price by using a pricecalculation module 110C on the basis of the information such as theprint form and print count for each selected image, and transmits thecalculated estimated price to the photosite 105 through the Internet104.

The photosite 105 receives the information of the estimated pricetransmitted from the printsite 109C in real time. If the portable browseuser has no personal information, the estimated price transmitted fromthe printsite 109C to the portable terminal 113A is transferred as Webinformation. If the portable browse user has personal information, thepresented price based on the estimated price factoring in points istransferred as Web information, thereby dynamically presenting the priceto the portable browse user who has given the print order.

When the portable browse user of the portable terminal 113A, who hasgiven the print order, approves of purchasing the service at thispresented price and returns an approval action to the photosite 105, thesettlement module 107 serving as a settlement means receives this andperforms settlement processing. When the settlement is completed, thephotosite 105 sends a formal print order to the printsite 109C. Theprintsite 109C receives this formal print order and acquires the imagedata required for printing out from the image database 117 in thephotosite 105. The image data acquired in this manner is printed out asprinted matter 112C by a printer 111C serving as a printing means ownedby the printsite 109C. The printed matter 112B is delivered, by sometransportation means, to the browse user of the portable terminal 113Awho has given the printout request.

The above description has been made on the outline of the informationproviding system designed to allow a user as the third party who hasreceived a permission to browse images or an album from a user who hasuploaded the images to browse the image data and give a print order onthe basis of the information received from the photosite 105.

<Arrangement of Database>

FIGS. 3 to 13 are views showing the contents of the database 118 managedby the photosite 105 in this embodiment.

FIG. 3 is a view showing a data table associated with the customerinformation managed by the photosite 105 in this embodiment. When a userexecutes user registration, one record of a customer information datatable 400 is created and registered and managed and registered in thedatabase 118 to be managed. For a registered user, a unique user ID isdefined, and the user is managed on the database by the customerinformation data table 400 using a user ID 401 as a key. The informationmanaged as customer information includes a notification destination mailaddress 402, login name 403, password 404, name (last name) 405, name(first name) 406, phonetic transcriptions in kana (last name) 407,phonetic transcriptions in kana (first name) 408, zip codes (1, 2) 409and 410, municipal division code 411, addresses (1, 2) 412 and 413,telephone numbers (1, 2, 3) 414, 415, and 416, and user registrationstate 417. When the user registration state 417 is 1, it indicates thatthe user has already been registered and is allowed to use thephotosite. When this information is 0, it indicates that the use of thephotosite is inhibited.

FIG. 4 is a view showing a customer state table for managing informationrepresenting the current state of each user who uses the photosite 105in this embodiment. When the user executes user registration, one recordof a customer state data table 500 is created and registered in thedatabase 118 to be managed. Each set value in this record is updatedwhenever necessary in accordance with the operation performed by theuser while using the photosite 105. When, therefore, the user logs in,the state set when the user used the photosite last is stored in thecustomer state data table 500. The data stored in this customer statedata table 500 include, by using a user ID 501 serving as a key, analbum ID 502 of the album that was displayed last by the user, a maximumdisc capacity 503, and a point 504 that is accumulated when the usergives a print order. With respect to the same user, the user ID 501 anduser ID 401 are equal in value.

FIG. 5 is a view showing the customer album data table managed by thephotosite 105 in this embodiment. When the user creates one new albumwhile using the photosite 105, one record of a customer album data table600 is created and registered in the database 118 to be managed. Whenthe user deletes an album, the corresponding record is deleted from theinformation database 118. The data stored in the customer album datatable 600 include, by using a user ID 601 of the registered user whichserves as a key, an album ID 602 of the album created by the user, and adisplay ordinal number 603 of the album. Note that with respect to thesame user, the user ID 601 and user ID 401 are equal in value.

FIG. 6 is a view showing the album information data table managed by thephotosite 105 in this embodiment. When the user creates a new albumwhile using the photosite 105, one record of an album information datatable 700 is created and registered in the information database 118 tobe managed. When the user deletes this album, the corresponding recordis deleted from the information database 118. The album information datatable 700 manages, by using an album ID 701 as a key, an album name 702,a file path 703 to a comment on the album, a disclosurepermission/inhibition flag 704 for the album, a passwordpermission/inhibition flag 705, an album password 706, a printpermission/inhibition flag 707, an original image displaypermission/inhibition flag 708, and a display form number 709. If thedisclosure permission/inhibition flag 704 for the album is 1, itindicates that the album can be disclosed. If this flag is 0, itindicates the inhibition of disclosure. If the flag is −1, it indicatesthat the disclosure of the album is inhibited by the managing operatorof the photosite. If the password permission/inhibition flag 705 is 1,it indicates the presence of a password. If this flag is 0, it indicatesthe absence of a password. If the password permission/inhibition flag705 is 1, the password is stored in the album password 706. If the printpermission/inhibition flag 707 is 1, it indicates the album can beprinted. If this flag is 0, it indicates that the album cannot beprinted. If the original image display permission/inhibition flag 708 is1, it indicates that display operation can be done. If this flag is 0,it indicates that display operation cannot be done. If the display formnumber 709 is 1, it indicates that the album is displayed in the form ofa list. If this flag is 2, it indicates that the album is displayed indetail. Note that with respect to the same album, the value stored inthe album ID 701 is equal to that in the album ID 602.

FIG. 7 is a view showing the album image data table managed by thephotosite 105 in this embodiment. Every time the user uploads one imageonto an album, one record of an album image data table 800 is increasedand registered in the information database 118 to be managed. When animage is deleted, the corresponding record is deleted from theinformation database 118. The data managed in the album image data table800 include an image ID 802 of an image stored in an album ID 801 and animage display number 803 indicating the display position of the image inthe album. Note that with respect to the same album, the ID stored inthe album ID 801 is equal to that in the album ID 701.

FIG. 8 is a view the image information data table managed by thephotosite 105 in this embodiment. Every time the user uploads an imageonto an album, one record of an image information data table 900 iscreated and registered in the information database 118 to be managed.When an image is deleted, the corresponding record is deleted from theinformation database 118. The data stored in the image information datatable 900 includes, by using an image ID 901 serving as a key, a user ID902 of the user who owns the image, an image name 903, a file path 904to the original image, a file path 905 to a thumbnail file, a file path906 to a display image, a path 907 to a comment file to the image, animage browse count 908, and an image print count 909. With respect tothe same image, the value stored in the image ID 901 is equal to that inthe image ID 802. With respect to the same user, the value stored in theuser ID 902 is equal to that in the user ID 401.

FIG. 9 is a view showing the order information data table managed by thephotosite 105 according to this embodiment. When a print order for analbum is placed, one record of an order information data table 1000 iscreated per order and registered in the database 118 to be managed. Thedata stored in the order information data table 1000 includes, by usingan order number 1001 serving as a key which is issued for each printorder, an orderer ID 1002, a receiver name 1003, destination zip codes(1, 2) 1004 and 1005, destination municipal code 1006, destinationaddresses (1, 2) 1007 and 1008, destination telephone numbers (1, 2, 3)1009, 1010, and 1011, a printsite ID 1012, an order date 1013, and anorder status 1014. If the order status 1014 is 0, it indicates that noorder has been given to the printsite. If it is 1, it indicates that anorder has been given to the printsite. If it is 2, it indicates thatdelivery has done.

FIG. 10 is a view showing the ordered image data table managed by thephotosite 105 according to this embodiment. When a print order for analbum is placed, records are created in an ordered image data table 1100in number equal to the number of images notified from the photosite 105to the printsite 109 in the process of giving the print order andregistered in the database 118 to be managed. The ordered image datatable 1100 manages, by using an order number 1101 as a key, a receiptnumber 1102 of the printsite 109, an image number 1103 managed on aprint order basis, file paths 1104, 1105, and 1106 to a thumbnail imagecopied for a print order, an original image, and an image for previewdisplay, a print count 1107, a print size 1108, a print type 1109, andan image ID 1110. “1”, “2”, “3”, “4”, and “5” set in the print size 1108respectively indicate L size, 2L size, postal card size, postcard size,and A4 size. “0” and “1” set in the print type 1109 respectivelyindicate a brimless print and brimmed print. With the respect to thesame order, the number stored in the order number 1101 is equal to thatin the order number 1001. The image ID 1110 indicates the image IDbefore coping, and in which the same value as that in the image ID 901is held.

FIG. 11 is a view showing the order settlement data table managed by thephotosite 105 according to this embodiment. One record of an ordersettlement data table 1200 is created per print order for an album andregistered in the database 118 to be managed. The order settlement datatable 1200 manages, by using an order number 1201 as a key, a settlementmethod 1202, a total price 1203, a print price 1204, a print pricebenefit 1205, a print tax charge 1206, a delivery charge 1207, adelivery tax charge 1208, a photosite benefit 1209, and a status 1210.In the settlement method 1202, “1” indicates transfer; “2”, cash ondelivery; and “3”, “credit settlement”. This embodiment will exemplifyonly the flow of processing for credit settlement. If the status 1210 is0, it indicates the completion of settlement. If this status is 1, itindicates an incomplete transaction. With respect to the same order, thevalue stored as the order number 1201 is equal to that stored as theorder number 1001.

FIG. 12 is a view showing the orderer data table managed by thephotosite 105 according to this embodiment. One record of an ordererdata table 1300 is created per print order for an album and registeredin the database 118 to be managed. The orderer data table 1300 manages,by using an orderer ID 1301 as a key, a user ID 1302, a notificationdestination mail address 1303, a name (last name) 1304, a name (firstname) 1305, a phonetic transcriptions in kana (last name) 1306, phonetictranscriptions in kana (first name) 1307, zip codes (1, 2) 1308 and1309, a municipal division code 1310, addresses (1, 2) 1311 and 1312,and telephone numbers (1, 2, 3) 1313, 1314, and 1315. If the orderer isnot a registered user of the photosite, 0 is assigned to the user ID1302. With respect to the same order, the ID stored in the orderer ID1301 is identical to that in the orderer ID 1002. If the orderer is amember of the photosite, the same ID is stored in the user ID 1302 anduser ID 401 with respect to the same orderer. In this case, as therespective pieces of user information in the fields 1303 to 1315, thevalues input as the corresponding pieces of user information in thecustomer information data table 400 having the same user ID 401 arecopied.

FIG. 13 is a view showing the printsite data table managed by thephotosite 105 according to this embodiment. When a new printsite thatcan be connected to the photosite 105 is constructed, a new record of aprintsite data table 1400 is created and registered in the database 118to be managed. The printsite data table 1400 manages, by using aprintsite ID 1401 as a key, a provider name 1402, a URL 1403 to a CGI(Common Gateway Interface) for notifying a temporary print order, a URL1404 to a CGI for notifying a formal print order, and a URL 1405 to aCGI for order cancellation.

FIGS. 14 to 17 are views showing the contents of databases 119A, 119B,and 119C managed by the printsites 109A, 109B, and 109C in thisembodiment. Note that since the printsites 109B and 109C have the samearrangement as that of the printsite 109A, only the arrangement of theprintsite 109A will be described below.

FIG. 14 is a view showing the contents of the database for managing theinformation of the photosite 105 which the printsite 109A has in thisembodiment. When a photosite 105 which can give an order to theprintsite 109A is constructed, a new record of a photosite data table1500 is created and registered in the database 119A. The photosite datatable 1500 manages a photosite ID 1501, a photosite name 1502, a URL1503 to a CGI for notifying an estimate, a URL 1504 to a CGI fornotifying exceptional processing such as deletion of an order orchanging of a price, and a URL 1505 to a CGI for notifying a printstatus.

FIG. 15 is a view showing the contents of an order data table which theprintsite 109A according to this embodiment has. Every time a temporaryprint order is issued from the photosite 105, one record of an orderdata table 1600 is created and registered in the database 119A to bemanaged. When the photosite 105 notifies an order delete request forthis record, it is deleted from the database 119A. The order data table1600 in the printsite 109A manages a receipt number 1601, a photosite ID1602 of the photosite 105 which has issued an order, an order number1603 of the photosite 105, a temporary print order date 1604, a formalprint order date 1605, an order status 1606, a print type 1607 to be setwhen a print order is placed, a print price 1608, a printsite bargainprice 1609, a print tax charge 1610, a delivery charge 1611, a deliverytax charge 1612, and a total price 1613. If the order status 1606 is 0,it indicates a temporary print order. If this status is 1, it indicatesthat a formal print order is placed but printing has not been done. Ifthe status is 2, it indicates that a formal print order is placed andprinting has been done. It the status is 3, it indicates that deliveryhas been done. If the status 4, it indicates that settlement has beenmade. If the print type 1607 is 0, it indicates a brimless print. If itis 1, it indicates a brimmed print.

FIG. 16 is a view showing the contents of a print image informationtable 1700 which the printsite 109A according to this embodiment has.When a temporary print order is issued from the photosite 105, recordsof a print image information table 1700 which the printsite 109A has arecreated in number corresponding to the image information contained inthe order and registered in the database 119A to be managed. When anorder delete request is notified from the photosite 105, thecorresponding record is deleted from the database 119A. The print imageinformation table 1700 in the printsite manages a receipt number 1701,an image number 1702, a URL 1703 on the photosite 105 which is used toacquire a print image file, a URL 1704 on the photosite 105 which isused to acquire a preview display image file, a URL 1705 on thephotosite 105 which is used to acquire a thumbnail image file to bedisplayed on a print order window when a temporary print order isplaced, a print count 1706, a print size 1707, a print status 1708, anda print unit price 1709. The images sent from the photosite 105 arenumbered when a temporary print order is placed, with the first imagebeing numbered 1. This number is stored in the image number 1702. “1”,“2”, “3”, “4”, and “5” set in the print size 1707 respectively indicateL size, 2L size, postal card size, postcard size, and A4 size. If theprint status 1708 is 0, it indicates that the image has not beenprinted. If this status is 1, it indicates that the image has beenprinted. With respect to the same print order, the number stored in thereceipt number 1701 is equal to that in the receipt number 1601.

FIG. 17 is a view showing the contents of an order delivery table whicha printsite has. When a formal print order is notified from thephotosite 105, one record of an order delivery table 1800 is created andregistered in the database 119A to be managed. The order delivery table1800 in the printsite manages an order number 1801, a receiver name1802, destination zip codes (1, 2) 1803 and 1804, a destinationmunicipal code 1805, destination addresses (1, 2) 1806 and 1807,destination telephone numbers (1, 2, 3) 1808, 1809, and 1810, a deliverydate 1811, and a status 1812. If the status 1812 is 0, it indicates thatdelivery has not been done. If this status is 1, it indicates thatdelivery has been done.

<Outline of Services>

The following services can be realized by the above system according tothis embodiment:

(1) user registration: performing registration for the use of thephotosite 105 by using the user PC 102A and making the photosite 105issue a user ID to the registered user;

(2) image data upload: transferring images from the user PC 102A to thephotosite 105;

(3) print order: sending an instruction to print image data from theuser PC 102A to the photosite 105 and printing an image through theprintsite 109A;

(4) notification of browse permission: sending e-mail from the user PC102A to the user PC 102B to permit the browsing of image data stored inthe photosite 105;

(5) browsing of image data: allowing a user to browse image data storedin the photosite 105 through the user PC 102B; and

(6) browsing of images from portable terminal: allowing a user to browseimage data stored in the photosite 105 through the portable terminal113A.

The contents of the respective services will be described in detailbelow. Note that the services and functions realized by the systemaccording to this embodiment are not limited those described above.

<Entrance of Photosite>

FIG. 18 shows an example of the window to be displayed first when a usertries to receive a service from the photosite 105 according to thisembodiment.

HTML data for displaying a window 1900 is stored in a storage medium inthe photosite 105. This data can be freely downloaded through theInternet 104. When, therefore, the user activates the Web browser 120Ain the user PC 102A and designates a URL representing the address of aWeb server, the window 1900 shown in FIG. 18 is displayed.

The areas and buttons arranged on the window 1900 are a userregistration button 1901, a login name input area 1902 which is usedwhen the user having undergone user registration uses the photosite 105,a password input area 1903, a login button 1904, an album ID input area1905 for album browsing, an album browse button 1906, a print order IDinput area 1907 for checking the status of a print order, and a printorder confirmation button 1908.

The processing to be performed when each button on the window 1900 ispressed will be described below.

<User Registration>

A procedure for user registration will be described first. When the userregistration button 1901 on the window 1900 is pressed, the processingshown in the flow chart of FIG. 19 is performed. FIG. 19 shows the flowchart representing processing in the photosite 105 at the time of userregistration. When the user registration button 1901 on the window 1900is pressed, a window 2100 shown in FIG. 20 is displayed, and userregistration processing is started (step S2001).

The window shown in FIG. 20 is a window for performing user registrationin this embodiment. This window includes a notification destinationaddress input area 2101 for a user to be registered, a login name inputarea 2102 for the user, a password input area 2103, name input areas2104 and 2105, input areas 2106 and 2107 for the phonetic transcriptionsof the name in kana, zip code input areas 2108 and 2109 for the user tobe registered, a municipal division selection area 2110, address inputareas 2111 and 2112, and telephone number input areas 2113, 2114, and2115. Although not shown in FIG. 19, when a cancel button 2117 ispressed, the window 1900 is restored without performing userregistration processing.

When the registration button 2116 is pressed, it is checked in stepS2002 whether data concerning necessary items have been input. Assumethat in this embodiment, the necessary items are the mail address 2101,login name 2102, password 2103, name (2104 and 2105), and telephonenumbers 2113, 2114, and 2115.

If it is determined that data concerning the necessary items have notbeen completely input in the photosite 105, an error window is displayedin step S2003. FIG. 21 is a view showing an error window 2200 to bedisplayed at this time. When an OK button 2201 is pressed, the window2100 is displayed again.

If it is determined in step S2002 that data concerning the necessaryitems have been input, the photosite 105 searches the customerinformation data table 400 in the database 118 (step S2004) to checkwhether the login name input in the input area 2102 has already beenused (step S2005).

If the Login name input in the input area 2102 has already been used, anerror window is displayed in step S2006. FIG. 22 shows an error window2300 displayed at this time. If an OK button 2301 is pressed, the window2100 is displayed again.

If the login name input in the input area 2102 is not found in thedatabase 118, a window 2400 shown in FIG. 23 is displayed to prompt theuser to input a password again (step S2007). If a cancel button 2403 ispressed, the registration processing is interrupted, and the window 2100is displayed, although not shown in FIG. 19.

If an OK button 2402 is pressed, it is checked whether the passwordinput in a password input area 2401 coincides with the password input inthe password input area 2103 on the window 2100 (step S2008).

If it is determined in step S2008 that the input password differs fromthe input characters, an error window 2500 shown in FIG. 24 is displayed(step S2009). If an OK button 2501 on this window is pressed, the window2400 is displayed again.

If it is determined in step S2008 that the input passwords coincide witheach other, the flow advances to step S2010 to display a userinformation confirmation window 2600.shown in FIG. 25, determining thatall the information necessary for user registration is input. Theinformation displayed on the window 2100 is the information input by theuser. If a correction button 2602 is pressed, the flow returns to stepS2001 to display the window 2100 again to allow the user to edit inputinformation.

If a confirmation button 2601 is pressed, the maximum value of thevalues of user IDs issued in the past is acquired from the customerinformation data table 400 in the database 118. The value obtained byadding 1 to the acquired value is the user ID of the user to be newlyregistered (step S2012).

In step S2013, a new customer information data table 400 is created onthe basis of the user ID obtained in step S2012, and the informationinput on the window 2100 is registered in the customer information datatable 400. That is, the contents of the input areas 2101, 2102, 2103,2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 21112, 2114, and 2115shown in FIG. 20 are respectively stored in the fields 402, 403, 404,405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, and 416 shown inFIG. 3. In addition, the user registration state 417 is set to 1.

When a user is newly registered, there are no album created by the useror uploaded image. When a user is newly registered, one each of recordof the customer album data table 600 shown in FIG. 5 and albuminformation data table 700 shown in FIG. 6 may be created and registeredin the database 118 in advance. In this case, the value obtained byadding one to the maximum value of the album IDs that have been issuedso far by the database 118 is set in the album ID 602. In addition, 1 isset in the display ordinal number 603, and a temporary album name, e.g.,“my album”, may be set as a default. In addition, obviously, the initialvalues determined by the photosite 105 are set in the album informationdata table 700.

When registration in the database 118 is completed, e-mail having thesame contents as those displayed on the window 2600 in FIG. 25 iscreated and transmitted to the e-mail address registered in the customerinformation data table 400 in FIG. 3 (step S2014). FIG. 26 shows anexample of the contents of the e-mail issued at this time.

<Login>

A procedure for allowing a user having undergone user registration forthe photosite 105 to actually receive a service from the photosite 105will be described next. Assume that in this embodiment, all the imagesuploaded by users are managed in the photosite 105 on a folder (calledan album) basis.

When the user inputs a login name and password in the login name inputarea 1902 and password input area 1903, respectively, and presses thelogin button 1904, the photosite 105 searches the customer informationdata table 400 in the database 118. Assume that no corresponding loginname is found in the customer information data table 400 or the passwordin the found record differs from the character string input in thepassword input area 1903. In this case, a warning window 2800 shown inFIG. 27 is displayed. If a button 2801 is pressed at this time, thewindow 1900 is displayed again.

If the password for the found record coincides with the character stringinput in the input area 1903, it is determined that the photosite inputuser is properly authenticated, and a window 2900 shown in FIG. 28 isdisplayed.

On the window 2900, a button 2901 is a button for changing userinformation. A button 2902 is a logout button. Buttons for editoperation for the album displayed on this window are arranged in an area2903. A button 2904 is a button for setting the properties of an album.A button 2905 is an album notification button. A button 2906 is a buttonfor newly creating an album. A button 2907 is a button for deleting analbum. A button 2908 is a button for uploading image data. A button 2909is a print order button. An area 2910 is an area in which buttons foralbum selection are displayed. On the head portion of this area, thedata sizes of images stored in the photosite are displayed, togetherwith its ratio to the allowable capacity. Buttons equal in number to thealbums created by the user are arranged below the head portion.

Referring to FIG. 28, buttons 2911 to 2915 indicate that five albumswere created by the user. When a given one of the buttons is pressed,the photosite 105 changes the images displayed in an album display area2923 in accordance with the selected album, and displays the album nameof the album on the upper left end of the album display area. An area2916 is an area in which buttons for editing the respective images inthe album are arranged. When a given one of buttons 2917 to 2922 ispressed, edit processing corresponding to the pressed button isperformed for one of the images displayed in the album display area 2923which corresponds the check box that is checked. The area 2923 is analbum image display area. In this area, the images stored in the albumare sequentially displayed, and check boxes corresponding to the imagesare arranged. When a displayed image is pressed, a property settingwindow for the image is displayed.

FIG. 29 is a flow chart showing a processing method for edit operationby a user after the window 2900 in FIG. 28 is displayed. The followingprocessing is performed in accordance with user operation on the window2900.

When a user input is received in step S3001, it is checked in step S3002whether the user input is an album edit instruction. If a button in thearea 2903 on the window 2900 is pressed, it is determined that the inputis an album edit instruction. In this case, the flow advances to albumedit processing in step S3003.

If it is determined in step S3002 that the user instruction is not analbum edit instruction, the flow advances to step S3004 to check whetherthe user input is an image edit instruction. If a button in the area2916 on the window 2900 is pressed, it is determined that the input isan image edit instruction, and the flow advances to step S3005. In stepS3005, processing like rotating 90° clockwise/counterclockwise,deleting, moving, copying, or changing the order is performed for theimage selected in the album.

If it is determined in step S3004 that the user input is not an imageedit instruction, the flow advances to step S3006 to check whether theuser input is a user information edit instruction. When the button 2901on the window 2900 is pressed, it is determined that the input is a userinformation edit instruction. When this button is pressed, the window2100 shown in FIG. 20 is displayed in step S3007 to allow the user tochange the registered information. The user information edit processingin this case is almost the same as the user registration processingdescribed in <User Registration> except that the pieces of informationregistered by the user are displayed as initial values when the windowis displayed, the window 2900 is displayed when the registration button2116 or cancel button 2117 is pressed, and registration of userinformation in the database amounts to the updating of existing userinformation instead of the registration of new information.

If it is determined in step S3006 that the user input is not a userinformation edit instruction, the flow advances to step S3008 to checkwhether the user input is an image selection instruction. If the userselects an image in the area 2923 on the window 2900 by, for example,clicking on the image with a mouse, it is determined that an image isselected, and the flow advances to image property edit processing instep S3009. As image property edit processing, editing of an image fileor comment can be done.

If it is determined in step S3008 that the user instruction is not animage selection instruction, the flow advances to step S3010 to checkwhether the user instruction is an album selection instruction. If abutton in the area 2910 on the window 2900 is pressed, it is determinedthat an album is selected, and album display processing in step S3011 isperformed.

If it is determined in step S3010 that the user input is not an albumselection instruction, it is checked in step S3012 whether the userinstruction is a logout instruction. If the button 2902 on the window2900 is pressed, it is determined that the user input is a logoutinstruction, and the flow advances to step S3010 to perform logoutprocessing. In performing logout processing, the photosite 105 registersthe currently displayed album ID in the last display album ID 502 in thecustomer state data table 500 in the database 118, thus updating thealbum ID. The displayed window is then restored to the window 1900.

If it is determined in step S3012 that the user input is not a logoutinstruction, the flow returns to step S3001 to wait for the next userinput.

Step S3003 (album edit processing) and step S3011 (album displayprocessing) will be described in detail below.

[Album Edit Processing]

FIG. 30 is a flow chart showing a procedure for album edit processing inthe photosite 105.

It is checked in step S3101 whether property setting is selected. If thebutton 2904 on the window 2900 is pressed, it is determined thatproperty setting is selected, and the flow advances to step S3102 todisplay a window 3200 shown in FIG. 31 to allow the user to set variousattributes associated with the selected album (the album displayed inthe album display area 2923 in FIG. 29 immediately before thisoperation).

If it is determined in step S3101 that property setting is not selected,the flow advances to step S3103 to check whether album notification isselected. If the button 2905 on the window 2900 is pressed, it isdetermined that album notification is selected, and the flow advances tostep S3104 to display a window 3300 shown in FIG. 32 to allow the userto make settings to notify, by e-mail, the third party of a method ofbrowsing the selected album.

If it is determined in step S3103 that album notification is notselected, it is checked in step S3105 whether creation of a new album isselected. If the button 2906 on the window 2900 is pressed, it isdetermined that creation of a new album is selected, and the flowadvances to step S3106 to display a window 3200 shown in FIG. 31. If anew album name (an album name that has not been registered by the loginuser) is input in an album name input area 3201 on the window 3200 and asetting button 3208 is pressed, a new album is created.

If it is determined in step S3105 that creation of a new album is notselected, it is checked in step S3107 whether deletion of an album isselected. If the button 2907 on the window 2900 is pressed, it isdetermined that deletion of an album is selected, and the flow advancesto step S3108. If the button 2907 is pressed, a window 3400 shown inFIG. 33 is displayed to allow the user to delete the selected album.

If it is determined in step S3107 that deletion of an album is notselected, it is checked in step S3109 whether uploading of an image to aselected album is selected. If the button 2908 on the window 2900 ispressed, it is determined that uploading of an image is selected, andthe flow advances to step S3110 to perform upload processing.

If it is determined in step S3109 that uploading of an image to an albumis not selected, it is checked in step S3111 whether print orderprocessing for an album is selected. If the button 2909 on the window2900 is pressed, it is determined that print order processing for analbum is selected, and the flow advances to step S3112 to perform printorder processing.

[Album Display Processing]

FIG. 34 is a flow chart showing processing associated with selection anddisplay of an album when one of the album selection buttons 2911 to 2915in the album selection area 2910 on the window 2900 is pressed.

It is checked in step S3501 which ordinal number the pressed button haswith respect to the head of the group of buttons, and the database 118is searched for the customer album data table 600 having this number inthe display ordinal number 603. The album ID 601 is then acquired asAlbumID. The album information data table 700 is specified from thealbum ID 601, thereby deriving album information.

In step S3502, the database 118 is searched for all the records in thealbum image data table 800 having AlbumID obtained in step S3501 in thealbum ID 801. The number of hits, i.e., found records, is represented byN, and 1 is assigned to an image count process variable I.

It is checked in step S3503 whether I≦N. The processing from step S3504to step S3509 is repeated while I≦N, thus displaying all the imageswithin the album.

In step S3504, the album image data table 800 having I in the imagedisplay number 803 is searched with the records found in the step S3502,and the image ID 802 of the image is obtained. When the image ID 802 isobtained, the database 118 is searched for a record in the imageinformation data table 900 having the image ID 802 in the image ID 901.

In step S3505, the path 905 to a thumbnail file of images is acquiredfrom the record found in step S3504.

In step S3506, it is checked whether the value of the display formnumber 709 in the album information data table 700 acquired in stepS3501 is 1. In this embodiment, if this value is 0, it indicatesthumbnail display. If the value is 1, it indicates detailed display.

If the display form number 709 is 1 in step S3506, the thumbnail imagesand the detailed information associated with the images are displayed instep S3507. In this embodiment, as the detailed information, the imagenames, comments, browse counts, and print counts from the imageinformation data table 900 are displayed, together with check boxes forimage edit processing. A window 3600 shown in FIG. 35 is an example ofalbum display when detailed display is performed. Since this window 3600is the same in function as the window 2900 except for the display methodof the album display area 2923, a detailed description thereof will beomitted.

If it is determined in step S3506 that the display form number 709 isnot 1, thumbnail images, image names, and image edit check boxes aredisplayed in step S3508. The window 2900 shown in FIG. 28 is an exampleof such a simple display.

If it is determined in step S3503 that I>N, since all the images in thealbum are displayed, the processing is terminated.

In the above embodiment, only the two display forms are described.Obviously, however, more display forms may be used.

<Image Upload>

Image upload processing with respect to a selected album will bedescribed next. When the upload button 2908 on the window 2900 ispressed, image upload processing is started. FIG. 36 is a flow chartshowing the flow of the processing of uploading images to a selectedalbum.

First of all, when the button 2908 on the window 2900 is pressed, thephotosite 105 calculates the number of files (Files) which the loginuser can add in the photosite 105. Since the resources of the photosite105 are limited, each login user can store images only to apredetermined capacity. No image file can be uploaded beyond thiscapacity.

Whether uploading can be done is determined by checking in step S3702whether “Files” is a positive integer. If “Files” is less than one, itis determined that uploading cannot be done, a window 3800 shown in FIG.37 is displayed (step S3703). When an OK button 3801 on the window 3800is pressed, the window 2900 is restored.

If “Files” is one or more, an upload window 3900 shown in FIG. 38 isdisplayed in step S3704. On this window, image sets, each constituted bya reference button 3901 for selection of a file in the user PC 102A, aninput area 3902 for inputting a file path, and a preview display area3903 for displaying a thumbnail image of a selected image, are displayedin number equal to the number of files (Files) that was calculated instep S3701. When a transmission button 3904 is pressed, the flowadvances to step S3705 to transfer the selected image files from theuser PC 102A to a work area in the photosite 105. Although no shown inthe flow chart of FIG. 36, when a cancel button 3905 is pressed, theupload processing is terminated, and the window 2900 is displayed.

The image files transferred to the photosite 105 are stored in thedatabase 117. Let N be the number of transferred files. In addition, theprocess variable I is set to 1 (step S3706).

It is checked in step S3707 whether I≦N. If I>N, the window 2900 isdisplayed in step S3716, and the processing is terminated.

If it is determined in step S3707 that I≦N, it is checked in step S3708whether the Ith transferred file is an image file that can be handled bythe photosite 105. In this embodiment, the transferred file isdetermined as a file that can be used by the photosite 105 only when theuploaded image is a JPEG file, and digital camera photographingcondition information in the DCF format can be extracted from its headerfield. If the transferred file is anything other than the above file, awindow 4000 shown in FIG. 39 is displayed in step S3709. In step S3710,this file set in the work area in the photosite 105 is deleted. Notethat when an image is printed in the printsite 109A, the DCF informationis used for color correction and the like for printing by using ashutter speed, information indicating whether electronic flash has beenused or not, and the like. When an OK button 4001 is pressed, the flowadvances to step S3715 to upload the next file.

If it is determined in step S3708 that the uploaded file is an imagefile having a predetermined format, the flow advances to step S3711 tocreate a thumbnail image of this image and store it from the work areain the photosite 105 to the image database 117.

It is then checked in step S3712 whether a file can be added. Thisdetermination is done by checking whether the maximum disk capacity isexceeded when the file in process is registered. If it is determined instep S3712 that no file can be added, the window 3800 shown in FIG. 37is displayed, and all the image files in the work area in the photosite105 which have not been registered in the image database 117 aredeleted. In step S3716, the window 2900 is displayed.

If it is determined in step S3712 that a file can be added, the imageinformation is registered in the database 118 in step S3714. Morespecifically, with respect to the uploaded image file, the imageinformation data table 900 shown in FIG. 8 is created in such a mannerthat the value obtained by adding one to the maximum image ID of all theimage IDs registered so far is set in the image ID 901 of the addedimage; a file path, in the original image file path 904; file paths tothe newly created thumbnail display image and display image, in thethumbnail file path 905 and display image file path 906, respectively;0, in the image browse count 908; and 0, in the image print count 909.The album image data table 800 is registered in which the album ID ofthe currently selected album is set in the album ID 801; the above imageID, in the image ID 802; and the value obtained by adding one to thenumber of images in the album, in the image display number 803.

I is incremented by one in step S3715, and the flow returns to stepS3707.

The processing from step S3707 to step S3715 is repeated while I isequal to or less than N, thereby registering uploaded image files in thedatabase to the maximum capacity.

FIG. 40 is a flow chart showing the processing of calculating the numberof files (Files) that can be added in step S3701.

First of all, in step S4101, the database is searched for the imageinformation data table 900 to extract records having the user ID of alogin user. Let N be the number of corresponding records. In addition, 1is assigned to the process variable I for image records, and 0 isassigned to a variable process Size for the calculation of the imagesize used by the user.

It is checked in step S4102 whether I≦N. If I≦N, the flow advances tostep S4103 to acquire an image file by using the original image filepath of the Ith record found in step S4101.

In step S4104, the size of the image file is added to Size, and 1 isadded to I in step S4105.

By performing the processing from step S4103 to step S4105 while I≦N,the disk capacity Size of the disk currently used by the user can becalculated.

In step S4106, the database 118 is searched for the user state datatable 500 with the user ID 501 of the login user, and the maximum diskcapacity 503 is set to Max₁₃ Size.

It is checked in step S4107 whether Size<Max₁₃ Size. If NO in stepS4107, since there is no disk area left for this user, 0 is assigned toFiles in step S4108.

If it is determined in step S4107 that Size<Max₁₃ Size, it is checked instep S4109 whether N is 0. If N is not 0, an average file size S of onefile of the user is obtained in step S4110 asS=Size/NIf N is 0, the average file size of images photographed by a widely useddigital camera with an average number of pixels is assigned to S in stepS4111. In this embodiment, an average image size of 500 kbytes (500000)obtained when images are photographed by 2,000,000-pixel digital camerasis assigned to S.

In step S4112, the number of albums that can be added (Files) iscalculated by dividing the remaining user disk capacity by the averagefile size. That is, “Files” is obtained byFiles=(Max₁₃ Size—Size)/S

It is checked in step S4113 whether Files=0. If Files=0, “Files” ischanged to Files=0 in step S4114.

In steps S4109 and S4110, as a file size that is expected to be used bythe user, the average of the sizes of image files that have already beenuploaded by the user is used. Only when no user image is uploaded, theaverage file size of images photographed by widely used digital cameraswith an average number of pixels is used. However, the average file sizeof images photographed by widely used digital cameras with an averagenumber of pixels may always be used. In this case, there is no need toperform determination in step S4109, and hence the flow directlyadvances from step S4107 to step S4111.

<Print Order>

FIG. 41 is a flow chart showing the flow of processing among the user PC102, the photosite 105, and the printsite 109 when the user gives aprint order by using the photosite 105. The user can give a print orderfor an image in a selected album in the photosite by pressing the printorder button 2909 on the window 2900. Note that the parenthesized stepsare the corresponding steps in FIG. 1.

When the user generates an album browse request in step S4201 (step S1),the photosite 105 reads out album images and presents them to the userin step S4202 (step S2). That is, on the window 2900, album imagescorresponding to a pressed album selection button in the album selectionarea 2910 are displayed in the album display area 2923.

In step S4203 (step S3), the user gives a print order instruction. Theprint order instruction is issued when the print order button 2909 onthe window 2900 is pressed.

When the print order instruction is issued, the flow advances to stepS4204, in which the photosite 105 creates a window 4300 for theselection of the printsite 109 shown in FIG. 42 and presents it to theuser PC 102.

When the user selects the printsite 109 from a printsite selection area4301 and presses an OK button 4302 in step S4205, the photosite 105issues a temporary print order to the printsite 109A selected by theuser in step S4206 (step S4). FIG. 53 shows an example of the data ofthe temporary print order issued to the printsite 109A. Although notshown in FIG. 41, if the user presses a cancel button 4303 in stepS4205, the processing is interrupted, and the photosite 105 displays thecurrently selected album on the window 2900 again. When a button 4304 ispressed, information about the currently selected printsite 109A isdisplayed.

Upon notification of the temporary print order, the printsite 109Acreates data for displaying an image selection window 4400 shown in FIG.43 and transmits the data to the user PC 102 in step S4207 (step S5).The window 4400 is a print order image selection window created by theprintsite 109A, and includes a selection area 4401 for the selection ofa print type (brimmed or brimless) at the time of printing, an area 4402in which a thumbnail image in the album acquired from the photosite 105is displayed, a selection area 4403 for the selection of a print size,an input area 4404 in which a print count is designated, an estimationrequest button 4405, and a cancel button 4406. Note that thumbnail imagedisplay areas 4402, size selection areas 4403, and print count inputareas 4404 exist in number equal to the number of image data containedin the temporary print order.

When the user selects an image to be ordered from the image selectionwindow 4400 and presses the estimation request button 4405 uponinputting a size and print count in step S4208, the flow advances tostep S4209 (step S6), in which the printsite 109A performs estimationcalculation processing. When estimation calculation is completed in stepS4209 (step S7), the corresponding information is notified to thephotosite 105. Note that an estimated price may be derived bycalculation. Alternatively, a table storing calculation results may beprepared, and an estimated price may be read out from the table.

If no estimation request is generated in step S4208, i.e., the cancelbutton 4406 on the window 4400 is pressed, the temporary print order inthe printsite 109A is deleted, and the photosite 105 is notified thatthe order is aborted. In step S4221, the photosite 105 cancels theorder, and stops the temporary print order processing. The window 2900is then restored.

When the estimate data is notified from the printsite 109A, thephotosite 105 reads out the cumulative points 504 from the customerstate data table 500 in the database 118 in the photosite 105, subtractsthe cumulative points from the estimated price, and displays the resultto the user. FIG. 44 shows the estimate window displayed at this time.In the case of a browse user including portable browse user, if there isno customer state data about the user, the printsite 109A displays theestimate data to the user.

When the estimate window is displayed, the user considers purchase instep S4211 (step S9). Referring to FIG. 41, this processing is brieflywritten as “purchase considered?” in step S4211. However, when the userconsiders purchase, the credit information shown in FIG. 45 and thedestination shown in FIG. 46 are input between the photosite and theuser. If the cancel button 4503, 4602, or 4702 is pressed during thisoperation, the flow shifts to order cancellation approval processing instep S4218. In this embodiment, since a uniform delivery charge is set,the above flow is used. If, however, different charges are set dependingon destinations, the window in FIG. 46 is displayed in the printsite109A before estimate calculation processing in step S4209 is performed.

If the user gives an order, the photosite 105 performs settlementprocessing in step S4212. In step S4213 (step S10), the photosite 105issues a formal print order to the printsite 109A.

Upon notification of the formal print order, the printsite 109A performsorder reception processing in step S4214. In step S4215, the printsite109A acquires image data from the photosite 105, and performs printprocessing for the image data in step S4216. In step S4217 (step S11), adelivery instruction is issued, and the processing is terminated.Although not shown in the flow chart of FIG. 41, when processing in stepS4214 to step S4217 is performed, the status of the printsite 109A isreturned to the photosite 105, and the corresponding information isstored in the database 118 in the photosite 105.

When the photosite 105 approves order cancellation in step S4218, thephotosite 105 gives a temporary print order delete request to theprintsite 109A. In step S4219, the printsite 109A deletes the temporaryprint order in accordance with this request.

FIG. 47 is a flow chart showing the contents of temporary print orderissue processing in the photosite 105 which is performed in steps S4204and S4206. FIG. 53 shows an example of the format of a temporary printorder issued by this processing.

When the print order button 2909 on the window 2900 is pressed, thephotosite 105 searches the album image data table 800 to acquire animage count N of the currently selected album in step S4801. Inaddition, 1 is assigned to a display image work counter I, and 0 isassigned to a selected image work counter J. The maximum order number ofthe order numbers of orders issued in the past is acquired from theorderer data table 1300 in the database 118, and the value obtained byadding one to the acquired number is set as an order number Order_ID ofthe current temporary print order.

In step S4802, the photosite 105 opens a work file (Work file) for thecreation of a temporary print order.

It is checked in step S4803 whether I≦N.

It is checked in step S4804 whether the Ith image is selected. If theuser has checked a check box, of the check boxes indicated by buttons2930 to 2935 on the window 2900, which is associated with the Ith image,it is determined that the Ith image is selected, and the flow advancesto step S4805.

In step S4805, the photosite 105 searches the album image data table 800in the database 118 for a record whose image display number is I, andacquires the image ID 802 of the image. The photosite 105 also searchesthe image information data table 900 for a record with image informationhaving the image ID 901. From the searched image information data table900, the photosite 105 acquires the file path 904 to the original image,the file path 905 to the thumbnail image, and the file path 906 to thedisplay image, and copies the respective images in a folder which can beaccessed from the printsite 109A.

In step S4806, the selected image counter J is incremented by one.

In step S4807, a sent image number J, the image name 903 acquired fromthe image information data table 900, and URLs for accessing theoriginal image, thumbnail image, and display image copied in step S4805from the printsite 109A are written in the Work file. In addition, theordered image data table 1100 is created and registered. At this time,Order_ID obtained in step S4801 is set to the order number 1101; J, tothe image number; and the file paths to the three copied images, to 1104to 1106. The remaining information in the record is set when an estimateis notified from the printsite 109A, and hence 0 is assigned to all theinformation.

In step S4808, I is incremented by one. If it is determined in stepS4804 that no image is selected, the flow also advances to step S4808.The flow then returns to step S4803. By repeating the processing in stepS4804 to step S4808 while I≦N, the identification information of allselected images for which a temporary print order is placed are writtenin the Work file.

If it is determined in step S4803 that 1>N, it is determined that theselection of the print order associated with all the images in the albumhas been checked, and the flow advances to step S4809 to check whetherJ=0, i.e., there is a selected image.

If it is determined in step S4809 that J=0, a window 4900 shown in FIG.48 is displayed in step S4810. When an OK button 4901 on the window 4900is pressed, the Work file is deleted in step S4816, and the orderedimage data table 1100 registered in step S4807 is completed deleted.Thereafter, the window 2900 is displayed.

If NO in step S4809, the flow shifts to step S4204 to perform displayprocessing for the printsite selection window 4300.

In step S4812, a user input is checked (as in step S4205). If the OKbutton 4302 on the window 4300 is pressed, the header field (up to<Estimeteitem> tag) of a temporary print order XML file 5401 shown inFIG. 53 shown in FIG. 53 is created in step S4813. In the header field,the above order number and J are respectively assigned toPhotositeOrderid and Count, but the remaining fields are fixed.

In step S4814, the Work file is merged with the temporary print orderXML file 5401. More specifically, elements expressed by <estimeteitem>tag and </estimeteitem> tag of the temporary print order XML data 5401are created by using the identification information of a selected imagein the Work file which is written by the processing in steps S4804 toS4808. By further adding the end tag of the order, the XML file 5401 tobe notified from the photosite 105 to the printsite 109A is completed.

In step S4815, the XML file created in steps S4813 and S4814 is notifiedto the printsite 109A. A destination CGI is acquired from the URL 1403to a temporary print order notification CGI in the printsite data table1400.

If the cancel button 4304 on the printsite selection window 4300 ispressed, since is it is determined in step S4812 that the OK button isnot pressed, the flow advances to step S4816 to delete the Work file. Instep S4807, the registered ordered image data table 1100 is completelydeleted. Thereafter, the window 2900 is displayed, and the processing isterminated.

FIG. 49 is a flow chart showing the contents of display processing for aprint image selection window in the printsite 109A in step S4207.

In step S5001, a temporary print order file is acquired from thephotosite 105.

In step S5002, the order data table 1600 is created and registered inthe database 119A. The value obtained by adding one to the maximum valueof the values of receipt numbers issued in the order data table 1600 isset in the receipt number 1601, and the photosite ID 1602 and photositeorder number 1603 are acquired from the acquired temporary print orderfile. The date when the temporary print order file was acquired is setin the temporary print order 1604, and 0 (temporary print order) isassigned to the order status. Of the items in the order data table 1600,the items 1607 to 1613 are registered when an estimate is issued, andhence 0 is set in all these items.

In step S5003, N and 1 are respectively assigned to the temporary printorder image count and the work image counter I.

It is checked in step S5004 whether I≦N. If I≦N, the flow advances tostep S5005.

In step S5005, the print image information table 1700 associated withthe Ith image written in the temporary print order file is created. Thesame value as the receipt number 1601 in step S5001 is set in thereceipt number 1701, and I is set in the image number 1702. As the URLs1703, 1704, and 1705, the corresponding URLs are acquired from thetemporary print order file and set. Of the items in the print imageinformation table 1700, the items 1705 to 1708 are registered when anestimate is issued, and hence 0 is set in all these items.

In step S5006, the thumbnail image acquired in step S5005 is acquiredfrom the photosite 105. In step S5007, the thumbnail image is displayedas the Ith image.

In step S5008, order count and order size input areas are created, and 1and L size are set as initial values. As items to be selected in theorder size input area, items are acquired from a service contents datalist 5800 shown in FIG. 57. The service contents data list 5800 is alist for setting service contents and corresponding unit prices inadvance in the printsite 109A.

In step S5009, I is incremented by one, and the flow shifts todetermination in step S5004. By repeating the processing in steps S5005to S5009 while I≦N, all the images registered in the temporary printorder can be displayed on the order window. If it is determined in stepS5004 that I≦N, the processing is terminated.

FIG. 50 is a flow chart showing estimate calculation in the printsite109 in step S4209 in FIG. 41 and notification of estimate information tothe photosite 105. FIG. 54 shows an example of the estimate informationthat is created by the printsite 109A and notified to the photosite 105.

In step S5101, the number of images displayed on the window 4400 isassigned to N; 1, to the work image counter I; 0, to the work orderimage count J; and 0, to a work total price Account.

In step S5102, a Work file is created.

In step S5103, it is checked whether I≦N. If I≦N, the flow advances tostep S5104.

In step S5104, the value of the input area 4404 associated with the Ithimage on the window 4400 is acquired, and it is checked whether thevalue is 0. If the value is not 0, the information set in the selectionarea 4403 is acquired in step S5105, and a unit price U corresponding tothe size is acquired from the corresponding paper size in the servicecontents data list 5800. If it is determined in step S5104 that theorder count is 0, the flow advances to step S5108.

In step S5106, the amount obtained by multiplying the image print countby U is added to Account.

In step S5107, the order estimate information associated with the Ithimage is added to the Work file. The print image information table 1700in the database 119A is searched for a record having the currentprintsite receipt number in the receipt number 1701 and I in the imagenumber 1702. The print count 1706 and print size 1707 of the foundrecord are updated by the current set values, and the print unit price1709 is updated by U. In addition, by adding the currently set printcount to J, the number of images for which print orders have been givenis stored.

In step S5108, I is incremented by one, and the flow returns to theprocessing in step S5103. By repeating the processing in steps S5104 toS5108 while I≦N, estimate information and a total price with respect toall the images can be obtained.

It is checked in step S5109 whether J=0. If J=0, since no print image isselected, a warning window is displayed in step S5115. The warningwindow displayed at this time is the same as the window 4900. When theOK button is pressed, the Work file is deleted in step S5116, and thewindow 4400 is displayed again.

If it is determined in step S5109 that J is not equal to 0, a pricecorresponding to a benefit, if any, in the printsite 109A is calculatedin step S5110. In this case, a printsite benefit list 5900 shown in FIG.58 is searched for a benefit. If there is a list corresponding to thesize IDs in the service contents data list, the user can receive adiscount written in “reduced price” in accordance with the print countin “benefit unit”.

In step S5111, the header field (up to <resultitem> tag) of an estimateXML file 5501 shown in FIG. 54 is created. PrintSiteOrderid is obtainedby adding “pr-” to the receipt number of the printsite 109A. J is inputto count. In addition, a print price, tax charge, delivery charge, anddelivery tax charge are added.

In step S5112, the contents of the Work file are merged with theestimate XML file 5501. If there is a benefit in the printsite 109A,benefit information is also added to this file, and the end tag of theestimate is finally added to the file, thereby completing the estimateinformation file 5501.

In step S5113, the order data table 1600 is searched for a record havingthe current printsite receipt number in the receipt number 1601. Theprint type 1607 of the found record is updated by the information inputin the type input area 4401 on the window 4400, and Account is assignedto the print price 1608. In addition, the bargain price and print taxcharge are respectively input to the printsite bargain price 1609 andprint tax charge 1610. Furthermore, the estimated delivery charge isinput to the delivery charge 1611, the delivery tax charge is input tothe delivery tax charge 1612, and the sum total of the values set in1608 to 1612 is set in the total price 1613, thus updating the record.

The estimate information created in step S5114 is notified from theprintsite 109A to the photosite 105.

FIG. 51 is a flow chart showing processing in the photosite 105 in theinterval between the instant at which the estimate notified from theprintsite 109A is acquired and the instant at which a formal print orderis issued in step S4213 in FIG. 41.

In step S5201, estimate data is acquired from the printsite 109A.

In step S5202, the cumulative points 504 are acquired from the customerstate data table 500 and assigned to Pt. In this embodiment, thecumulative points are converted into yen at a conversion rate of one yenper point. In addition, the value of Pt is assigned to a processvariable New_Pt for the calculation of a point after the end of theorder. In the case of a browse user including a portable browse user, ifthere is no customer state data with respect to the user, 0 is assignedto Pt.

In step S5203, the estimated total price for printing in the printsite109A which is acquired from the estimate data is assigned to Price.

It is checked in step S5204 whether Price<Pt. If Price<Pt, Price isassigned to Pt.

In step S5206, the estimate is displayed. A window 4500 shown in FIG. 44is an example of the estimate display window displayed at this time. Inan estimate display area 4504, print prices are displayed on a printpaper basis, and benefit information in the printsite 109A is displayednext. In addition, a tax charge, total price (print price) to be paid tothe printsite 109A, delivery charge, and delivery tax charge are added,and benefit information in the photosite 105 is added, therebydisplaying the amount to be paid by the user. Although not shown, in thecase of a browse user including a portable browse user, if there is nocustomer state data with respect to the user, a benefit informationbutton 4501 is not displayed.

When the benefit information button 4501 is pressed, it is determined instep S5207 that changing of the benefit information is selected, and abenefit information setting window 5300 shown in FIG. 52 is displayed toallow the user to determine whether to use a benefit for this payment(step S5205). If a radio button 5301 on the window 5300 is selected, thecurrent points are used as a benefit. If a radio button 5302 is set, thepoints input in a point input area 5304 can be used as a benefit. If aradio button 5303 is selected, the benefit is not reflected in theestimate. If an OK button 5305 is pressed, the flow returns to stepS5204 to perform addition processing for points again. If a cancelbutton 5306 is pressed, the flow returns to step S5206 to display thewindow 4500, although not shown in FIG. 51.

If a cancel button 4503 on the window 4500 is pressed, the flow shiftsfrom step S5209 to step S5210 to perform delete processing for thetemporary print order. In this processing, the order information datatable 1000 associated with the print order and the image informationdata table 900 which are registered in the photosite 105 are deleted,and the printsite 109A is notified of the deletion of the temporaryprint order. The window 2900 is then restored.

When a credit information setting button 4502 is pressed, the flowshifts from step S5209 to step S5211 to subtract the point count usedthis time from the current point count as New_Pt and add 1% of Price.

In step S5212, a window 4600 shown in FIG. 45 is displayed to make theuser give a print order and set information for payment. When an orderbutton 4601 on the window 4600 is pressed, a window 4700 shown in FIG.46 is displayed to prompt the user to input a destination. In the caseof a browse user including a portable browse user, if there is nocustomer state data with respect to the user, “the same destination asorderer” is not displayed. When an order button 4701 on the window 4700is pressed, the photosite 105 updates the respective tables in thedatabase 118. First of all, the value of New_Pt is stored in thecumulative points 504 in the customer state data table 500. That is, thepoint count used for this order is subtracted, and then a point count tobe added for this print order is added. In the case of a browse userincluding a portable browse user, if there is no customer state datawith respect to the user, the customer state data table 500 is notupdated. The order information about each image is acquired from theestimate information file acquired from the printsite 109A, and theprint count, print size, and print type of the record of eachcorresponding image in the ordered image data table 1100 are updated. Inaddition, a new order settlement data table 1200 is created on the basisof the current order number, and the contents displayed in an estimatedisplay area 4504 on a window 4500 are registered in the table. “1”indicating the completion of settlement is assigned to the status 1210.Furthermore, an orderer data table 1300 is created, and the currentorderer information is acquired from the customer information data table400 and copied to the orderer data table 1300. Lastly, an orderinformation data table 1000 is created, and the destination informationinput on the window 4700 is registered in the table. “1” indicating thatan order has been given to the printsite is assigned to the order status1014.

The flow then advances to step S5213, in which the photosite 105notifies the printsite 109A of a formal print order. FIG. 55 is a viewshowing an example of the formal print order XML data that is notifiedat this time. Note that this notified data 5601 is almost the same dataobtained by adding a destination to the estimate data 5501 shown in FIG.54 and changing each tag name.

In step S5214, order contents are displayed, and the orderer is notifiedof the contents by mail. FIG. 56 shows a display window 5700 of theorder contents. When a button 5701 is pressed, the photosite 105displays the window 2900. FIG. 59 shows an example of the mail to benotified when a print order is placed. Although not shown, in the caseof a browse user including a portable browse user, if there is nocustomer state data with respect to the user, mail notification is notperformed.

FIG. 60 is a flow chart showing the details of order receptionprocessing in step S4214 in FIG. 41.

First of all, in step S6101, order information is acquired and an ordernumber is extracted from the order information to search for the orderdata table 1600 having the order number. Order notification time is setin the formal print order date 1605 in the order data table 1600, andthe order status 1606 is changed to 1 indicating that no imagecorresponding to the formal order has been printed. Destinationinformation is further acquired from the acquired order information.

In step S6102, the acquired information is registered in the orderdelivery table 1800. The status 1812 is set to 0 indicating thatdelivery has not been done.

<Notification of Album>

FIG. 32 is a view showing the window displayed when the notificationbutton 2905 on the window 2900 is pressed.

When the user inputs a destination mail address 3302, sender mailaddress 3303, mail title 3304, and message 3305 on a window 3300 andpresses a notification button 3306, the photosite 105 merges the abovecontents with the mail document created in the photosite 105 and issuesalbum notification mail to the destination mail address.

FIG. 61 shows an example of the album notification mail. The URL andalbum ID contained in the notification mail are the same as the URL onthe window 3300 and the contents displayed in a disclosure album IDdisplay area 3308. Upon reception of the mail, the user can browse analbum by designating the URL written in the mail. By inputting the albumID written in the mail in the album ID input area 1905 on the window1900 and presses the OK button 1906, the user can also browse the samealbum as that browsed when the URL is designated. In this case, thevalue of parameter AlbumID=written in the URL is equal to the album IDof the disclosure album. A window 7800 shown in FIG. 72 is a window usedto access an album through the portable terminal 113 that can beconnected to the Internet. The user can browse the album by inputtingthe album ID in an input area 7801.

<Creation of Disclosure Album>

A procedure for creating a disclosure album ID will be described next. Adisclosure album ID needs to have a value from which the third partycannot easily guess or infer the original album ID 701 and thedisclosure album ID of another album on the basis of thenumber/character string of the ID.

For this purpose, a disclosure album ID must be created by encrypting analbum ID managed in the photosite 105. In this case, as indicated by theflow chart of FIG. 64, in step S6501, the album ID is multiplied by 70,and a check digit is embedded in the value at the units place of theproduct. In steps S6502 to S6507, the resultant data is converted into acharacter string that can be easily input through the portable terminal113. This makes it difficult for the third party to infer anotherdisclosure album ID.

[Embedding of Check Digit]

FIG. 62 is a flow chart showing the processing of embedding a checkdigit in step S6501 in FIG. 64. In this embodiment, the value obtainedby multiplying the album ID 701 by seven to ID, and the value at eachdigit place of ID expressed in decimal is multiplied by the number ofdigits. The sum total of the products is then obtained, and a complementto the value at the units place is set as a check digit. Each digit ofID is carried by one, and the check digit is added to the units place,thus obtaining a new ID.

In step S6301, the album ID 701 of the album for which a notification isto be currently done is obtained, and the value obtained by multiplyingthe ID by seven is assigned to ID.

In step S6302, a process variable Div in which the quotient obtained bysequentially dividing ID by 10 is stored is initialized to ID; a processvariable Order for counting the number of digits of ID, to 1; a processvariable Rem in which the remainder obtained by sequentially dividing IDby 10 is stored, to 0; and a process variable Check for check digitcalculation, to 0.

In step S6303, it is checked whether Div is 0. If Div is not 0, the flowadvances to step S6304.

In step S6304, the remainder of the quotient obtained by dividing Div by10 is assigned to Rem, the quotient obtained by dividing Div by 10 isassigned to Div, and Rem×Order is added to Check.

In step S6305, one is added to Order, and the flow returns to stepS6303. By repeating the processing in steps S6304 and S6305 until Divbecomes 0, a sum total Check of the products of the numerical values atthe respective digit places of ID and the number of digits iscalculated.

If it is determined in step S6303 that Div is 0, the flow advances tostep S6306, in which the remainder of the quotient obtained by dividingCheck by 10 is subtracted from 10, and the resultant value is assignedto Check.

In step S6307, the value obtained by multiplying ID by 10 and addingCheck to the product is set as a new ID.

The numerical values before and after ID obtained in this manner do notbecome album IDs. Even if a given person tries to search for otheralbums by manipulating the acquired disclosure album ID, the photosite105 can detect such unauthorized access and reject album display.

<Conversion for Telephone>

The processing in step S6502 and the subsequent steps in FIG. 64 will bedescribed next. In this processing, an encrypted disclosure album ID isconverted into a character string that can be easily input by a smallnumber of keys. In this embodiment, a character string in whichcharacters input by the same button (e.g., A and B) do not consecutivelyappear is created by referring to a list 6400 for managing charactercodes corresponding to the respective numerical values of a telephone.

In the telephone/alphabet list 6400 in FIG. 63, the buttons (Button) ofa telephone, character codes (Letters) corresponding to the buttons, andthe numbers (AL) of character codes corresponding to the respectivebuttons are managed. The number AL of character codes corresponding to abutton X is represented by AL[X].

In this embodiment, a disclosure album ID is created by selectingalphabetical characters one by one from the ID (numerical value) createdin step S6501.

More specifically, the first character is determined by converting theID into a base-26 number (using, for example, a table in which 0 to 25are assigned to A to Z), and each of the second and subsequentcharacters is selected from alphabetical characters that can be input bybuttons different from the button used to input the immediatelypreceding character that was determined. As a consequence, the ID isconverted into a base-23 or base-22 number to create a character string.This processing will be sequentially described below.

In step S6502, 1 is set as an initial value in a process variable Buttonindicating the button to be selected; 1, in a process variablePrev_Button indicating the immediately preceding button that waspressed; ID, in a process variable Div representing the quotientobtained by dividing ID by the number of types of characters that can beused; 0, in the process variable Rem representing the remainder obtainedby dividing ID by the number of types of characters that can be used;and a null character string, in a character string Str that is finallyobtained.

It is checked in step S6503 whether Div is 0. At first, since ID isassigned to Div in step S6502, the flow advances to step S6504.

In step S6504, Div is divided by the number of characters that can becurrently used, and the quotient and remainder are respectively set inDiv and Rem. In the initial state, Prev_Button is 1 and AL[Prev_Button]is 0 according to the table shown in FIG. 63, and hence 26 types ofcharacters can be used. Thereafter, 22 or 23 types of characters can beused in accordance with the value of Button.

In step S6505, the character chr is determined on the basis of the valueof Rem and Prev_Button. That is, the (Rem)th character in allalphabetical characters except for alphabetical character assigned tothe immediately preceding button is determined as chr. Furthermore,button number Button to which chr belongs is also derived.

In step S6506, chr is added to Str.

In step S6507, Button is set in Prev_Button (i.e., the currentlyselected button becomes an immediately preceding button with respect tothe next button), and the flow returns to the processing in step S6503.Characters chr are added to the character string Str one by one byrepeating the processing in steps S6504 to S6507 until Div becomes 0.

If it is determined in step S6503 that Div becomes 0, Str becomes acharacter string representing a disclosure album ID.

FIG. 65 is a flow chart showing the processing of obtaining thecharacter chr corresponding to Rem and the button number Button to whichthe character belongs in step S6505 in FIG. 64.

In step S6601, the process variables Sum and Button are initialized into−1 and 1, respectively.

In step S6602, it is checked whether Button is equal to Prev_Button. Ifthey are equal, since the corresponding button cannot be used, the flowadvances to step S6604. If they are not equal, the number of charactersAL[Button] that can be input by using Button is added to Sum. That is,the number obtained by sequentially adding the numerical values in theAL column in the list 6400 in FIG. 63 is input to Sum. In this case, ALcorresponding to the immediately preceding button is not added by theprocessing in step S6602.

In step S6604, it is checked whether Sum<Rem. If Sum<Rem, 1 is added toButton, and the flow returns to step S6602. If Rem≦Sum, since there is acharacter corresponding to Rem in Button, the flow advances to stepS6606.

In step S6606, chr is obtained. Note that chr is the(Rem−Sum+AL[Button])th character in Letters[Button].

<Browsing of Album>

The user who has received the notification mail shown in FIG. 61 candisplay the album browse start window 6700 shown in FIG. 66 bydesignating a URL 6201 written in the mail document. Note that thiswindow can also be displayed by inputting an album ID 6203 written inthe notification mail in the album ID input area 1905 and pressing the“GO!” button 1906 on the window 1900.

FIG. 68 is a flow chart showing the processing of checking, upondesignation of an album ID by the user through the portable terminal113, whether an album corresponding to the designated album ID exists.

In step S7401, the number of digits of the input ID is initialized toOrder; the process variable I for counting the number of digits, to 1;the process variable Chr representing a character, to the character atthe first digit place; and AlbumID to be obtained, to 0. In thisembodiment, input parameters representing an album ID are limited toEnglish letters. If, however, unauthorized input, e.g., input ofcharacters other than English letters, is checked, an error window 7501shown in FIG. 69 is displayed as in the case wherein no albumcorresponding to the designated album ID exists.

In step S7402, a button to which the character of Chr is assigned issearched from the portable terminal button/alphabet list 6400 and set toBN.

In step S7403, a specific ordinal number in the alphabet to which Chrcorresponds is obtained, 1 is subtracted from the obtained value, andthe resultant value is set in Num.

In step S7404, it is checked whether I<Order.

If it is determined in step S7404 that I<Order, the character at the(i+1)th digit place is set in Prev_Chr.

In step S7406, a button to which the character of Prev_Chr is assignedis searched from the portable terminal button/alphabet list 6400 and isset in BP.

In step S7407, PB is compared with BN. Although not shown, in thisembodiment, since two characters assigned to the same button are notconsecutively input, if BP=BN, an error window 7500 is displayed.

If it is determined in step S7407 that BP<BN, only AL[BP] is subtractedfrom Num in step S7408. If it is determined in step S7407 that BP≧BN,the flow advances to step S7409 without performing the processing instep S7408.

In step S7409, the value obtained by subtracting only AL[BP] from 26 isset in a process variable Mult representing a multiplier.

In step S7410, AlbumID is multiplied by Mult, and Num is added to theproduct. The resultant value is then set as new AlbumID.

In step S7411, 1 is added to I, and BP and Prev_Chr are respectivelyassigned to BN and Chr. The flow then returns to the processing in stepS7403.

If it is determined in step S7404 that I is not larger than Order, thevalue obtained by multiplying AlbumID by 26 and adding Num to theproduct is newly set in AlbumID. If the album ID input by the user is acorrect value, AlbumID obtained here becomes ID shown in FIG. 62. Inthis embodiment, since this value is the value obtained by embedding acheck digit at the first digit place of the product of the existingalbum ID and 7, the quotient obtained by dividing Album by 10 is set inID in step S7413. It is then checked in step S7414 whether ID can bedivided by 7 without a remainder.

If it is determined in step S7414 that ID is divided by 7 without aremainder, ID is divided by 7 in step S7415.

In step S7416, the check digit embedding processing shown in FIG. 62 isperformed for this ID. In step S7417, it is checked whether ID coincideswith AlbumID.

If it is determined in step S7414 that ID cannot be divided by 7 withouta remainder, and it is determined in step S7417 that ID does notcoincide with AlbumID, it indicates that a proper album ID is not input.In step S7418, therefore, the error window 7500 shown in FIG. 69 isdisplayed.

The photosite 105 analyzes AlbumID of the parameter portion of the aboveinput URL or the album ID input to the album ID input area 1905. Onlywhen an album exists, the photosite 105 searches the album informationtable 700 for a record having the ID obtained in step S7414 in the albumID 701. The photosite 105 then searches the customer album data table600 for a user ID having the album ID, and further searches the customerinformation table for a record corresponding to the user ID 401.

Subsequently, the name (last name) 405 is displayed on a window 6700shown in FIG. 66. If the password permission/inhibition flag 705 of thealbum information data table 700 searched in this case indicates that apassword is set for the album, a password input area 6701 is displayed.Obviously, if no password is set for the album, a password input area6701 is not displayed.

When the OK button 6701 is pressed, for example, an album browse window6800 shown in FIG. 67 is displayed with respect to an album for which nopassword is set or an album for which a password is properly input. Thecontents of this window are the same as those of the album display area2923 on the window 2900. If a password is not properly input, the window2500 shown in FIG. 24 is displayed. When the OK button 2501 is pressed,the window 6700 is displayed again.

In addition, the value of the print permission/inhibition flag 707 isacquired from the album information data table 700, and a button 6803 isdisplayed in association with an album that can be printed, therebyallowing the user to give a print order. In this case, the flow of printorder processing is almost the same as login user processing (theprocessing to be done when the button 2909 on the window 2900 in FIG. 28is pressed) except that no point is added in the photosite 105.

<Browsing from Portable Terminal>

A window 7600 shown in FIG. 70 is an example of the window displayed onthe display of the portable terminal 113 at the time of browsing fromthe portable terminal. In response to a browse request from the user,the photosite 105 acquires the information of the terminal which hasgenerated the request to check whether the browse request has beengenerated by a portable terminal or PC. If the browse request isgenerated by the portable terminal, the window 7600 shown in FIG. 70 isdisplayed. Note that the contents of this window are the same as thoseof the window 6700. The window 7600 is displayed when the user directlydesignates the URL indicated by the notification mail shown in FIG. 72.This window is also displayed when the user inputs the album ID shown inFIG. 62 in an album ID input area 7801 on a window 7800 shown in FIG. 72and selects a button 7802.

When a button 7602 on the window 7600 is pressed, a window 7700 shown inFIG. 71 is displayed. The photosite 105 displays an image with a reducedimage size. In addition, the images in the album are separated from eachother to be displayed one by one in accordance with selection of a nextimage or previous image. When a button 7701 is pressed, detailedinformation such as an image name and comment is displayed. The contentsof this display are the same as those displayed with respect to eachimage shown in FIG. 35. In addition, the displayed images in the albumcan be updated one by one by pressing buttons 7702 and 7703.

Other Embodiment

The above embodiment has exemplified the case wherein the user browsesimages from the PC or portable terminal. However, the present inventionis not limited to this, and the user may access the informationproviding system from any kind of terminal, such as a fixed telephone,which can perform data communication.

In addition, the above embodiment has exemplified the method ofconverting numerical values into an. alphabetical character string.Obviously, however, numerical values can be converted into hiraganacharacter string by using a table in which buttons and the types ofhiragana characters assigned to the buttons are stored. In a generaltelephone (especially a cell phone), five characters, e.g., “

” to “

”, are assigned to buttons 1 to 7 and 9 (i.e., AL in FIG. 63 is 5), andthree characters and “

”, “

”, and “

” or “

”, “

”, and “

” are assigned to buttons 0 and 8 (i.e., AL in FIG. 63 is 3).

In the above embodiment, according to the description of step S2012 inFIG. 19, a user ID is compulsorily given as a login name to the user. Inthis case, however, a user ID may be converted into a character stringby the processing in steps S6502 to S6507 in FIG. 64, and the characterstring may be given as a login name to the user.

In addition, as the order number written on the window 5700 shown inFIG. 56 and in the order contents shown in FIG. 59, a character stringthat can be easily input by a cell phone may be provided. In this case,the state of a print order is presented upon confirming that thecharacter string is input in the input area 1907 on the window 1900shown in FIG. 18.

By performing such character string conversion in this manner,user-friendlier services can be provided for the user who uses aterminal with a smaller number of keys, e.g., a cell phone or fixedtelephone. The object of the present invention is achieved even bysupplying a storage medium (or recording medium) which stores softwareprogram for implementing the functions of the above-describedembodiments to a system or apparatus and causing the computer (or a CPUor MPU) of the system or apparatus to read out and execute the programcodes stored in the storage medium. In this case, the program codes readout from the storage medium implements the functions of theabove-described embodiments by themselves, and the storage medium whichstores the program codes constitutes the present invention. Thefunctions of the above embodiments are realized not only when thereadout program codes are executed by the computer but also when the OS(Operating System) or the like running on the computer performs part orall of actual processing on the basis of the instructions of the programcodes.

The functions of the above embodiments are also realized when theprogram codes read out from the storage medium are written in the memoryof a function expansion board inserted into the computer or a functionexpansion unit connected to the computer, and the CPU of the functionexpansion board or function expansion unit or the like performs part orall of actual processing on the basis of the instructions of the programcodes.

When the present invention is applied to the above storage medium, thestorage medium stores program codes corresponding to the flow chartsdescribed above (shown in FIG. 65 and/or FIG. 66).

As has been described above, according to the above embodiments, aninformation providing system which can easily update pricescorresponding to data processing, an information providing apparatus, aninformation providing method, a control program, and a storage mediumcan be provided.

As many apparently widely different embodiments of the present inventioncan be made without departing from the spirit and scope thereof, it isto be understood that the invention is not limited to the specificembodiments thereof except as defined in the appended claims.

1-9. (canceled)
 10. An information providing apparatus comprising: acreation unit configured to create ID data; a storage unit configured tostore a number and characters assigned to each key of a plurality ofkeys of a communication apparatus; and a conversion unit configured toconvert the ID data to a character string, on the basis of the numberand characters assigned to each key which are stored in said storageunit, such that two consecutive characters in the character string arerespectively assigned to different keys of the plurality of keys. 11.The apparatus according to claim 10, wherein said conversion unitcomprises a selection unit configured to extract characters constitutingthe character string one by one and, in a case where a currentlyselected character is assigned to a key to which an immediatelypreceding selected character is assigned, to change the currentlyselected character into a different character assigned to another key.12. The apparatus according to claim 10, wherein said communicationapparatus is a telephone, and the plurality of keys includes at leastbuttons to which numbers 0 to 9 are assigned.
 13. The apparatusaccording to claim 10, further comprising an information provision unitconfigured to provide predetermined information to the communicationapparatus in accordance with a character string input by thecommunication apparatus.
 14. An information processing method comprisingthe steps of: creating ID data; storing a number and characters assignedto each key of a plurality of keys of a communication apparatus in astorage unit; and converting the ID data to a character string, on thebasis of the number and characters assigned to each key which are storedin said storage unit, such that two consecutive characters in thecharacter string are respectively assigned to different keys of theplurality of keys.
 15. The method according to claim 14, wherein saidconverting step comprises the step of: extracting charactersconstituting the character string one by one and, in a case where acurrently selected character is assigned to a key to which animmediately preceding selected character is assigned, changing thecurrently selected character into a different character assigned toanother key.
 16. The method according to claim 14, wherein saidcommunication apparatus is a telephone, and the plurality of keysincludes at least buttons to which numbers 0 to 9 are assigned.
 17. Themethod according to claim 14, further comprising a step of providingpredetermined information to the communication apparatus in accordancewith a character string input by the communication apparatus.
 18. Acomputer-executable program stored on a computer-readable medium, theprogram causing a computer to perform the steps of: creating ID data;storing a number and characters assigned to each key of a plurality ofkeys of a communication apparatus in a storage unit; and converting theID data to a character string, on the basis of the number and charactersassigned to each key which are stored in said storage unit, such thattwo consecutive characters in the character string are respectivelyassigned to different keys of the plurality of keys.
 19. The programaccording to claim 18, wherein said converting step comprises the stepof: extracting characters constituting the character string one by oneand, in a case where a currently selected character is assigned to a keyto which an immediately preceding selected character is assigned,changing the currently selected character into a different characterassigned to another key.
 20. The program according to claim 18, whereinsaid communication apparatus is a telephone, and the plurality of keysincludes at least buttons to which numbers 0 to 9 are assigned.
 21. Theprogram according to claim 18, wherein the program causes a computer toperform a step of providing predetermined information to thecommunication apparatus in accordance with a character string input bythe communication apparatus.